Check if Codex CLI is available for code execution tasks
AI agents call codex_status to retrieve information from ML Lab MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a status check, which is a read-only query operation. It retrieves information about whether the Codex CLI is available but does not execute code, modify state, or trigger external operations. The low severity reflects that even if misused, status checks have minimal blast radius—they cannot corrupt data, execute arbitrary operations, or cause financial impact.
From the tool's definition Tool name is 'codex_status' and description states it 'Check[s] if Codex CLI is available' — a query operation that checks system state without modifying anything.
Attacks that exploit this kind of access
Check if Codex CLI is available for code execution tasks. It is categorised as a Read tool in the ML Lab MCP MCP Server, which means it retrieves data without modifying state.
Register the ML Lab 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 ML Lab MCP. Nothing to install.
codex_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
codex_status is provided by the ML Lab MCP server (pushpullcommitpush/ml-mcp). 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 →