Delete every conversation whose title contains query. Requires confirm=True.
AI agents call delete_conversations_matching to permanently remove resources in Codex Chats — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (conversations) and cannot be undone. It is classified as Destructive rather than Execute because the primary action is permanent deletion. The blast radius is significant—a poorly crafted query pattern could delete many conversations unintentionally.
From the tool's definition Tool name 'delete_conversations_matching' combined with description 'Delete every conversation whose title contains `query`' explicitly performs irreversible deletion.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete every conversation whose title contains query. Requires confirm=True. It is categorised as a Destructive tool in the Codex Chats MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Codex Chats MCP server in PolicyLayer and add a rule for delete_conversations_matching: 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.
delete_conversations_matching is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_conversations_matching 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 delete_conversations_matching. 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.
delete_conversations_matching 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 →