Critical Risk →

kaiten_cache_invalidate_all

Invalidate all caches

How to control kaiten_cache_invalidate_all ↓

What kaiten_cache_invalidate_all does on Kaiten

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

Critical Risk

Why kaiten_cache_invalidate_all needs a policy

Cache invalidation irreversibly destroys cached data across all caches. While the underlying source data is unaffected, all cached state is permanently wiped and cannot be recovered (caches must be rebuilt from scratch). This is a destructive operation with broad blast radius ('all caches') that could impact performance and availability if misused.

From the tool's definition Invalidate all caches

Risk signalsBulk/mass operation — affects multiple targets

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

How to control kaiten_cache_invalidate_all

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

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

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

  1. Create a free account and register Kaiten — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about kaiten_cache_invalidate_all

What does the kaiten_cache_invalidate_all tool do? +

Invalidate all caches. It is categorised as a Destructive tool in the Kaiten 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 kaiten_cache_invalidate_all? +

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

What risk level is kaiten_cache_invalidate_all? +

kaiten_cache_invalidate_all 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 kaiten_cache_invalidate_all? +

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

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

kaiten_cache_invalidate_all is provided by the Kaiten MCP server (vsaranyuk/kaiten-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kaiten tool call.

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

Free to start. No card required.

8 Kaiten tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.