clear_git_cache

THE RISK

Critical Risk

Why clear_git_cache needs a policy

Clearing cached Git repositories is a destructive action because it permanently removes data (cached repository contents) and cannot be undone. While the data can theoretically be re-fetched, the cached state is destroyed. This is more severe than a Write operation because it involves deletion.

From the tool's definition Tool name is 'clear_git_cache' and description states it will 'Clear all cached Git repositories to free up disk space.' This is an irreversible deletion operation that removes cached data without option to recover it.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access clear_git_cache gives an agent:

POLICY

How to control clear_git_cache

PolicyLayer is an MCP gateway — it sits between your AI agents and CodeRAG, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_git_cache:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_git_cache"
  ]
}

clear_git_cache disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register CodeRAG — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More CodeRAG tools

Destructive delete_edge Delete an edge by ID Destructive delete_node Delete a code node by ID Write initialize_semantic_search Initialize semantic search infrastructure including vector indexes Write scan_dir Scan a directory for source files and populate the graph Write scan_remote_repo Scan a remote Git repository and populate the graph database. Supports GitHub, GitLab, Bit Write add_edge Add a relationship edge between two nodes Write add_file Parse a single source file and add its entities to the graph Write add_node Add a new code node (class, interface, method, etc.) to the graph

All 38 CodeRAG tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in CodeRAG → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about clear_git_cache

What does the clear_git_cache tool do? +

Clear all cached Git repositories to free up disk space. It is categorised as a Destructive tool in the CodeRAG 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 clear_git_cache? +

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

What risk level is clear_git_cache? +

clear_git_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 clear_git_cache? +

Yes. Add a rate_limit block to the clear_git_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 clear_git_cache completely? +

Set action: deny in the PolicyLayer policy for clear_git_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 clear_git_cache? +

clear_git_cache is provided by the CodeRAG MCP server (jonnoc/coderag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CodeRAG tool call.

Start from CodeRAG, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →