Unarchive a Codex Cloud chat (return it to the active list).
AI agents use unarchive_chat to create or update resources in Codex Chats — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Codex Chats environment.
This tool modifies data state reversibly—unarchiving restores visibility of a chat without deleting or creating new data. It is a Write operation (state modification), not Read (no side effects), Execute (no command/code execution), Destructive (reversible), or Financial. Severity is low because the operation is easily reversible and has minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'unarchive_chat' and description 'Unarchive a Codex Cloud chat (return it to the active list)' indicate a state-change operation that reverses an archive action by moving a chat from archived to active status.
Attacks that exploit this kind of access
Unarchive a Codex Cloud chat (return it to the active list). It is categorised as a Write tool in the Codex Chats MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Codex Chats MCP server in PolicyLayer and add a rule for unarchive_chat: 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 Chats. Nothing to install.
unarchive_chat is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unarchive_chat 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 unarchive_chat. 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.
unarchive_chat is provided by the Codex Chats MCP server (shoyu-ramen/codex-chats-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 →