Clear a conversation history
AI agents call gemini_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.
Clearing conversation history permanently removes stored multi-turn chat session data. This action cannot be undone (the conversation history is lost), making it Destructive. Severity is medium because the blast radius is limited to conversation history data rather than production systems or financial assets, but misuse by an AI agent could inadvertently wipe ongoing or important chat sessions.
From the tool's definition 'Clear a conversation history' — clearing history is an irreversible deletion of stored conversation data
Attacks that exploit this kind of access
Clear a conversation history. 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 gemini_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.
gemini_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 gemini_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 gemini_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.
gemini_clear_conversation is provided by the Gemini MCP Server MCP server (jeff-emmett/gemini-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 →