Invalidate spaces cache
AI agents invoke kaiten_cache_invalidate_spaces to trigger actions in Kaiten. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Cache invalidation triggers an internal operation (clearing/resetting cached data) rather than simply reading data. It has side effects on the system's state (cache is cleared, forcing fresh data retrieval on next access), but does not delete user data, move money, or create/modify persistent records. It falls under Execute as it triggers an external/internal operation.
From the tool's definition Invalidate spaces cache
Documented attack patterns abuse exactly the kind of access kaiten_cache_invalidate_spaces gives an agent:
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_spaces:
{
"version": "1",
"default": "deny",
"tools": {
"kaiten_cache_invalidate_spaces": {
"limits": [
{
"counter": "kaiten_cache_invalidate_spaces_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}kaiten_cache_invalidate_spaces stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Invalidate spaces cache. It is categorised as a Execute tool in the Kaiten MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kaiten MCP server in PolicyLayer and add a rule for kaiten_cache_invalidate_spaces: 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.
kaiten_cache_invalidate_spaces is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the kaiten_cache_invalidate_spaces 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 kaiten_cache_invalidate_spaces. 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.
kaiten_cache_invalidate_spaces 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.
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.