AI agents invoke codex_skill_run 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.
This tool executes code (Codex skills) as background jobs. Execution of arbitrary or attacker-controlled skills could trigger unauthorized operations, resource consumption, or malicious behavior. It is categorized as Execute rather than Destructive because the tool itself doesn't inherently delete or overwrite data irreversibly; the risk depends on what the skill does.
From the tool's definition Tool name 'codex_skill_run' combined with description 'Run a Codex skill as a BACKGROUND job' indicates execution of arbitrary skills.
Attacks that exploit this kind of access
Run a Codex skill as a BACKGROUND job. Reads the skill. 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_skill_run: 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_skill_run 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_skill_run 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_skill_run. 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_skill_run 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.
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 →