Get round-trip statistics for this session
AI agents call codex_stats to retrieve information from Codex Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistical data about the current session (round-trip times, performance metrics, etc.). It performs a read-only query operation with no capability to modify state, execute code, delete data, or affect external systems. The low severity reflects minimal risk: session statistics are non-sensitive operational metadata, and misuse would only expose performance telemetry.
From the tool's definition Tool name 'codex_stats' and description 'Get round-trip statistics for this session' indicate retrieval of session metrics/telemetry data with no modification or side effects.
Attacks that exploit this kind of access
Get round-trip statistics for this session. It is categorised as a Read tool in the Codex Bridge MCP Server, which means it retrieves data without modifying state.
Register the Codex Bridge MCP server in PolicyLayer and add a rule for codex_stats: 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 Bridge. Nothing to install.
codex_stats 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_stats 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_stats. 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_stats is provided by the Codex Bridge MCP server (ndcorder/claude-codex-team). 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 →