Clear all documents from the RAG system
AI agents call clear_documents 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 all documents from the RAG system, which is irreversible data loss. The scope is comprehensive ('all documents'), making it high-severity. While not financial, this is clearly destructive—more severe than Write or Execute—as it obliterates data with no recovery mechanism described. High confidence due to unambiguous destructive semantics in both name and description.
From the tool's definition Tool name 'clear_documents' combined with description 'Clear all documents from the RAG system' indicates irreversible deletion of all documents without selective filtering or undo capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all documents from the RAG system. 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_documents: 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_documents 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_documents 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_documents. 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_documents 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 →