Clears the embeddings cache, forcing a complete reindex on next search or manual index operation. Useful when encountering cache corruption or after major codebase changes.
AI agents call c_clear_cache to permanently remove resources in Heuristic — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call c_clear_cache doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Heuristic is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Clears the embeddings cache, forcing a complete reindex on next search or manual index operation. Useful when encountering cache corruption or after major codebase changes. It is categorised as a Destructive tool in the Heuristic MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Heuristic MCP server in PolicyLayer and add a rule for c_clear_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 Heuristic. Nothing to install.
c_clear_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the c_clear_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.
Set action: deny in the PolicyLayer policy for c_clear_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.
c_clear_cache is provided by the Heuristic MCP server (softerist/heuristic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.