Grok Build 1.0.13 (5e9a58528b76) ignores documented CLI allow rules in leader-mode interactive sessions.
Reproduction on Linux:
- Start the leader with
grok --permission-mode default --allow "MCPTool(agent_sessions__*)" agent leader.
- Start its interactive TUI with
grok --leader --session-id <id>.
- Invoke the
agent_sessions__list_peers MCP tool.
Observed: the TUI prompts Allow (Agent Sessions) List Peers? even though the leader argv contains the matching rule. As a control, adding the same --allow "MCPTool(agent_sessions__*)" to the TUI argv still produces the prompt. The profile was already initialized and had no competing permission rule.
The documented matcher grammar is MCPTool(server__tool), and the exact tool identity here is agent_sessions__list_peers. The permissions guide says CLI --allow rules are always enforced. GROK_CONFIG / GROK_CONFIG_PATH is not a launch-scoped workaround because the documented overlay drops [permission].
Expected: leader-mode sessions should honor CLI allow rules in their session permission pipeline. If that is intentionally unsupported, please document a non-mutating, launch-scoped surface that can supply permission rules to a leader-mode TUI.
Until then, operators must persist [permission] allow = ["MCPTool(agent_sessions__*)"] in user or trusted-project Grok configuration (or approve each tool interactively).
Grok Build 1.0.13 (5e9a58528b76) ignores documented CLI allow rules in leader-mode interactive sessions.
Reproduction on Linux:
grok --permission-mode default --allow "MCPTool(agent_sessions__*)" agent leader.grok --leader --session-id <id>.agent_sessions__list_peersMCP tool.Observed: the TUI prompts
Allow (Agent Sessions) List Peers?even though the leader argv contains the matching rule. As a control, adding the same--allow "MCPTool(agent_sessions__*)"to the TUI argv still produces the prompt. The profile was already initialized and had no competing permission rule.The documented matcher grammar is
MCPTool(server__tool), and the exact tool identity here isagent_sessions__list_peers. The permissions guide says CLI--allowrules are always enforced.GROK_CONFIG/GROK_CONFIG_PATHis not a launch-scoped workaround because the documented overlay drops[permission].Expected: leader-mode sessions should honor CLI allow rules in their session permission pipeline. If that is intentionally unsupported, please document a non-mutating, launch-scoped surface that can supply permission rules to a leader-mode TUI.
Until then, operators must persist
[permission] allow = ["MCPTool(agent_sessions__*)"]in user or trusted-project Grok configuration (or approve each tool interactively).