List active in-memory sessions with recency and activity summary. Useful when running multiple clients against one bridge process.
AI agents call codex_sessions 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 queries and retrieves information about active sessions without modifying state, executing code, or triggering external operations. It has no side effects and presents minimal risk if misused by an AI agent—the worst outcome would be information disclosure about which sessions are active. This is a standard Read category operation.
From the tool's definition Tool description states 'List active in-memory sessions' with 'recency and activity summary.' The verb 'list' and the informational nature (no creation, modification, deletion, or code execution) clearly indicates a read-only operation that retrieves session…
Attacks that exploit this kind of access
List active in-memory sessions with recency and activity summary. Useful when running multiple clients against one bridge process. 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_sessions: 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_sessions 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_sessions 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_sessions. 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_sessions 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 →