// MCP TOOL REFERENCE

MCP CODEX WORKER TOOLS

5 tools from the Mcp Codex Worker MCP Server, categorised by risk level.

WRITE TOOLS

message-task Send a follow-up message to an existing task on its original session. Use this to steer a running task, refine completed work, or add instructions... 2/5

DESTRUCTIVE TOOLS

cancel-task Cancel one or more running tasks. Accepts a single task_id or an array. Running tasks are aborted and marked `cancelled`. Already-terminal tasks a... 4/5

EXECUTE TOOLS

respond-task Unblock a task that is in `input_required` because the agent requested input or an approval. Payload shape is discriminated by `type` — must match... 3/5 spawn-task Create and start a provider-agnostic task, returning a task_id you can track. (v1.0.34) Dispatches the prompt to the provider registered for the g... 4/5 wait-task Block until a task settles or asks for input. Returns as soon as the task reaches a terminal state (`completed`, `failed`, `cancelled`) or enters ... 3/5

// FAQ

How many tools does the Mcp Codex Worker MCP server have? +

The Mcp Codex Worker MCP server exposes 5 tools across 3 categories: Write, Destructive, Execute.

How do I enforce policies on Mcp Codex Worker tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Mcp Codex Worker server.

What risk categories do Mcp Codex Worker tools fall into? +

Mcp Codex Worker tools are categorised as Write (1), Destructive (1), Execute (3). Each category has a recommended default policy.

Enforce policies on Mcp Codex Worker

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →