Clear all cache data from the LLM response cache storage
AI agents call clear_cache to permanently remove resources in Lightrag — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes cached data without the ability to restore it. While the blast radius is limited to cached LLM responses (not the primary knowledge graph), the irreversible nature of clearing 'all' cache data makes this Destructive rather than Write.
From the tool's definition Tool name is 'clear_cache' with description 'Clear all cache data from the LLM response cache storage'. The verb 'clear' combined with 'all cache data' indicates irreversible deletion of stored data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all cache data from the LLM response cache storage. It is categorised as a Destructive tool in the Lightrag MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lightrag MCP server in PolicyLayer and add a rule for 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 Lightrag. Nothing to install.
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 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 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.
clear_cache is provided by the Lightrag MCP server (lightrag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →