AI agents call clear_context to permanently remove resources in Gemini Context MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call clear_context doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Gemini Context MCP Server is gone — there is no undo for destructive operations.
Documented attack patterns abuse exactly the kind of access clear_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gemini Context MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_context:
{
"version": "1",
"default": "deny",
"hide": [
"clear_context"
]
}clear_context disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Clear the context for a session. It is categorised as a Destructive tool in the Gemini Context MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gemini Context MCP Server MCP server in PolicyLayer and add a rule for clear_context: 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 Context MCP Server. Nothing to install.
clear_context 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_context 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_context. 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_context is provided by the Gemini Context MCP Server MCP server (ogoldberg/gemini-context-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Gemini Context MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 Gemini Context MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.