codex_status · Codex MCP: Risk & Policy

WHAT IT DOES

What codex_status does on Codex

AI agents invoke codex_status 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.

WHY IT NEEDS A POLICY

Why codex_status needs a policy

The description is nearly empty ('Run'), so confidence is low. However, based on the tool name 'codex_status' and its context among tools like exec, kill, poll, and list_jobs, it most likely retrieves the status of a running job (Read). But 'Run' in the description hints at execution.

From the tool's definition Tool name 'codex_status' and server description mentions 'status' as one of 8 Codex tools; description is 'Run' which is uninformative

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

codex_status Rate-limited

codex_status 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_status": {
      "limits": [
        {
          "counter": "codex_status_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Codex, so you can run agents against it safely.

FAQ

Questions about codex_status

What does the codex_status tool do? +

Run. 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.

How do I enforce a policy on codex_status? +

Register the Codex MCP server in PolicyLayer and add a rule for codex_status: 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.

What risk level is codex_status? +

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

Can I rate-limit codex_status? +

Yes. Add a rate_limit block to the codex_status 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_status completely? +

Set action: deny in the PolicyLayer policy for codex_status. 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_status? +

codex_status is provided by the Codex MCP server (pigowenhsiao/codex-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.