High-risk tools in Mcp Codex Worker
3 of the 5 tools in Mcp Codex Worker are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
respond-taskExecute 3/5Unblock a task that is in `input_required` because the agent requested input or an approval. Payload shape is discriminated by `type` — must match the pending question from `wa...
-
spawn-taskExecute 4/5Create 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 given `task_type` (Codex, Copil...
-
wait-taskExecute 3/5Block until a task settles or asks for input. Returns as soon as the task reaches a terminal state (`completed`, `failed`, `cancelled`) or enters `input_required`. If `timeout_...
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Mcp Codex Worker
Enforce policy on Mcp Codex Worker
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init