clear_all_caches

Clear all internal caches. Destructive — prefer smart_cache_cleanup.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/clear-all-caches.md

WHAT IT DOES

What clear_all_caches does on Jshookmcp

AI agents call clear_all_caches to permanently remove resources in Jshookmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why clear_all_caches is rated Critical

Irreversibly removes cached data; cannot be undone without rebuilding caches.

From the tool's definition Clear all internal caches. Destructive

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clear_all_caches safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_all_caches, this is the rule to start with:

clear_all_caches Hidden

clear_all_caches is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every clear_all_caches call is checked against it from then on.

FAQ

Questions about clear_all_caches

What does the clear_all_caches tool do? +

Clear all internal caches. Destructive — prefer smart_cache_cleanup. It is categorised as a Destructive tool in the Jshookmcp 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_all_caches? +

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

What risk level is clear_all_caches? +

clear_all_caches 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_all_caches? +

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

Set action: deny in the PolicyLayer policy for clear_all_caches. 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_all_caches? +

clear_all_caches is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools → Critical-risk tools on this server →

Across the catalogue

clear_project_index on ACE-MCP →clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →cancel_all_orders on Lighter MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →