Critical Risk →

remove_all_documents

Remove all documents from the index

How to control remove_all_documents ↓

What remove_all_documents does on Mcp Rag

AI agents call remove_all_documents to permanently remove resources in Mcp Rag — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why remove_all_documents needs a policy

This tool permanently deletes all indexed documents in a single operation. The action is irreversible and constitutes data destruction at scale. While not financial or involving code execution, it is more severe than a Write operation (which is reversible) due to its destructive and non-recoverable nature.

From the tool's definition Tool name 'remove_all_documents' combined with description 'Remove all documents from the index' indicates irreversible deletion of an entire dataset without targeted selection.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access remove_all_documents gives an agent:

How to control remove_all_documents

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_all_documents:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_all_documents"
  ]
}

remove_all_documents disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Mcp Rag — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about remove_all_documents

What does the remove_all_documents tool do? +

Remove all documents from the index. It is categorised as a Destructive tool in the Mcp Rag MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_all_documents? +

Register the Mcp Rag MCP server in PolicyLayer and add a rule for remove_all_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 Mcp Rag. Nothing to install.

What risk level is remove_all_documents? +

remove_all_documents is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_all_documents? +

Yes. Add a rate_limit block to the remove_all_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.

How do I block remove_all_documents completely? +

Set action: deny in the PolicyLayer policy for remove_all_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.

What MCP server provides remove_all_documents? +

remove_all_documents is provided by the Mcp Rag MCP server (kwanleefrmvi/mcp-rag-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Rag tool call.

Start from Mcp Rag, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

5 Mcp Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.