Clear LightRAG internal cache
AI agents call clear_cache to permanently remove resources in LightRAG MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing a cache permanently removes cached data that may be expensive or impossible to regenerate. This is an irreversible bulk operation affecting all cached entries in the LightRAG system, making it Destructive with high severity given the potential blast radius on the knowledge graph and RAG pipeline performance/state.
From the tool's definition 'Clear LightRAG internal cache' — clearing cache is an irreversible purge of stored data
Attacks that exploit this kind of access
Clear LightRAG internal cache. It is categorised as a Destructive tool in the LightRAG MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LightRAG MCP Server 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 MCP Server. 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 MCP server (lalitsuryan/lightragmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
clear_cache is one line of LightRAG MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →