AI agents invoke codex_dispatch to trigger actions in Codex. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The server description states 'async dispatch' as a core feature, and the tool name 'codex_dispatch' strongly implies it triggers asynchronous execution of Codex CLI tasks. Sibling tools like 'codex_cancel' and 'codex_status' further support a pattern of dispatching, monitoring, and cancelling operations. Since Codex CLI can execute code and shell commands, this tool likely triggers such execution.
From the tool's definition Tool name 'codex_dispatch' and sibling tools suggest async dispatch of Codex CLI commands; server description mentions 'async dispatch' explicitly.
Attacks that exploit this kind of access
codex_dispatch. It is categorised as a Execute tool in the Codex MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Codex MCP server in PolicyLayer and add a rule for codex_dispatch: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Codex. Nothing to install.
codex_dispatch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the codex_dispatch rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for codex_dispatch. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
codex_dispatch is provided by the Codex MCP server (shilong20/codexmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →