Critical Risk →

gemini_delete_cache

Delete a content cache

Risk signalsPermanently removes cached content

Part of the MCP Gemini server.

gemini_delete_cache can permanently delete data in MCP Gemini, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MCP GEMINI →

Free to start. No card required.

AI agents may call gemini_delete_cache to permanently remove or destroy resources in MCP Gemini. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call gemini_delete_cache in a loop, permanently destroying resources in MCP Gemini. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "gemini_delete_cache"
  ]
}

See the full MCP Gemini policy for all 41 tools.

Get this rule live on your own MCP Gemini server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCP GEMINI →

View all 41 tools →

These attack patterns abuse exactly the kind of access gemini_delete_cache gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so gemini_delete_cache only ever does what you allow.

SECURE MCP GEMINI →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the gemini_delete_cache tool do? +

Delete a content cache. It is categorised as a Destructive tool in the MCP Gemini MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on gemini_delete_cache? +

Register the MCP Gemini MCP server in PolicyLayer and add a rule for gemini_delete_cache: 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 MCP Gemini. Nothing to install.

What risk level is gemini_delete_cache? +

gemini_delete_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gemini_delete_cache? +

Yes. Add a rate_limit block to the gemini_delete_cache 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.

How do I block gemini_delete_cache completely? +

Set action: deny in the PolicyLayer policy for gemini_delete_cache. 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.

What MCP server provides gemini_delete_cache? +

gemini_delete_cache is provided by the MCP Gemini MCP server (mcp-gemini-crunchtools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Gemini tool call.

Deterministic rules across all 41 MCP Gemini tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.