CLEAR CONVERSATION HISTORY - Deletes specified conversation session and all associated message history. Frees memory and resets context. USAGE: Pass conversationId from start_conversation or chat response. Returns confirmation or
AI agents call clear_conversation to permanently remove resources in Gemini MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes conversation data without the ability to undo or recover it. While the blast radius is scoped to a specific conversation (not system-wide), the irreversibility and data loss nature classify it as Destructive rather than Write. An AI agent with misuse access could delete important conversation records that users rely on, causing data loss.
From the tool's definition The tool description explicitly states it 'Deletes specified conversation session and all associated message history' — the verb 'Deletes' combined with 'all associated message history' indicates irreversible removal of data.
Attacks that exploit this kind of access
CLEAR CONVERSATION HISTORY - Deletes specified conversation session and all associated message history. Frees memory and resets context. USAGE: Pass conversationId from start_conversation or chat response. Returns confirmation or. It is categorised as a Destructive tool in the Gemini MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gemini MCP Server MCP server in PolicyLayer and add a rule for clear_conversation: 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 Gemini MCP Server. Nothing to install.
clear_conversation 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 clear_conversation 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 clear_conversation. 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.
clear_conversation is provided by the Gemini MCP Server MCP server (mintmcqueen/gemini-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
clear_conversation is one line of Gemini MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →