Return this session
AI agents call whoami to retrieve information from Codex Peers MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool simply returns information about the current session. This is a pure read/query operation with no modification, execution, or destructive capability. Misuse potential is minimal since it only exposes session identity data.
From the tool's definition "Return this session" — retrieves identity/session info with no side effects
Attacks that exploit this kind of access
Return this session. It is categorised as a Read tool in the Codex Peers MCP MCP Server, which means it retrieves data without modifying state.
Register the Codex Peers MCP server in PolicyLayer and add a rule for whoami: 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 Peers MCP. Nothing to install.
whoami 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 whoami 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 whoami. 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.
whoami is provided by the Codex Peers MCP server (jscianna/codex-peers-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 →