clear_collection
Clear all indexed data from the collection. Use with caution - this is destructive.
This record as markdown: /tools/0xrdan-mcp-rag-server/clear-collection.md
What clear_collection does on MCP RAG Server
AI agents call clear_collection to permanently remove resources in MCP RAG Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why clear_collection is rated Critical
This tool performs an irreversible deletion of all data in a collection without granular targeting. While not financial or involving code execution, it permanently removes stored information with no undo capability, matching the Destructive category. The severity is high because the blast radius affects the entire knowledge base but is scoped to a single collection.
From the tool's definition Tool description explicitly states 'Clear all indexed data from the collection. Use with caution - this is destructive.' The action irreversibly removes all indexed data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs clear_collection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP RAG Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_collection, this is the rule to start with:
clear_collection is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP RAG Server, apply this rule, and every clear_collection call is checked against it from then on.
Questions about clear_collection
Clear all indexed data from the collection. Use with caution - this is destructive. It is categorised as a Destructive tool in the MCP RAG Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP RAG Server MCP server in PolicyLayer and add a rule for clear_collection: 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 MCP RAG Server. Nothing to install.
clear_collection 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_collection 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_collection. 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_collection is provided by the MCP RAG Server MCP server (0xrdan/mcp-rag-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP RAG Server, and thousands of servers like it.
Across the catalogue