codex_dispatch

Run formal Codex PM through local Codex OAuth/session with bounded dispatch receipts.

SERVERNogra SOURCE@nograai/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-nograai-nogra-mcp/codex-dispatch.md

WHAT IT DOES

What codex_dispatch does on Nogra

AI agents invoke codex_dispatch to trigger actions in Nogra. 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.

RISK

Why codex_dispatch is rated High

This tool executes a formal process (Codex PM) through an OAuth/session mechanism, which constitutes triggering an external operation. The execution is bounded (mitigating risk to some degree) but remains an Execute action because it runs code/operations whose effects depend on context.

From the tool's definition Tool description states "Run formal Codex PM" and "dispatch" suggests triggering external operations. The phrase "bounded dispatch receipts" indicates the tool executes actions with measurable effects that are recorded.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs codex_dispatch safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nogra, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For codex_dispatch, this is the rule to start with:

codex_dispatch Rate-limited

codex_dispatch stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "codex_dispatch": {
      "limits": [
        {
          "counter": "codex_dispatch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nogra, apply this rule, and every codex_dispatch call is checked against it from then on.

FAQ

Questions about codex_dispatch

What does the codex_dispatch tool do? +

Run formal Codex PM through local Codex OAuth/session with bounded dispatch receipts. It is categorised as a Execute tool in the Nogra MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on codex_dispatch? +

Register the Nogra 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 Nogra. Nothing to install.

What risk level is codex_dispatch? +

codex_dispatch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit codex_dispatch? +

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.

How do I block codex_dispatch completely? +

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.

What MCP server provides codex_dispatch? +

codex_dispatch is provided by the Nogra MCP server (@nograai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nogra, and thousands of servers like it.

This server

All 45 Nogra tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →