delete_documents

THE RISK

Critical Risk

Why delete_documents needs a policy

Deletion of documents cannot be undone without external backups or recovery mechanisms. This is a destructive operation that permanently removes indexed data. While the blast radius is limited to the specific collection and requires explicit IDs (reducing accidental misuse risk somewhat), the irreversible nature of document deletion and the potential to remove important indexed knowledge or embeddings justifies…

From the tool's definition Tool description explicitly states 'Delete specific documents from a collection by their IDs' — the verb 'delete' combined with permanent removal of data from a vector database collection represents an irreversible operation.

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

POLICY

How to control delete_documents

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_documents"
  ]
}

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

Create a free account and register Qdrant MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Qdrant MCP Server tools

Destructive clear_git_index Delete all indexed git history data for a repository. This is irreversible and will remove Destructive clear_index Delete all indexed data for a codebase. This is irreversible and will remove the entire co Destructive delete_collection Delete a collection and all its documents. Write index_new_commits Incrementally index only new commits since the last indexing. Much faster than full re-ind Write index_codebase Index a codebase for semantic code search. Automatically discovers files, chunks code inte Write index_git_history Index a repository Write reindex_changes Incrementally re-index only changed files. Detects added, modified, and deleted files sinc Write add_documents Add documents to a collection. Documents will be automatically embedded using the configur

All 20 Qdrant MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Qdrant MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_documents

What does the delete_documents tool do? +

Delete specific documents from a collection by their IDs. It is categorised as a Destructive tool in the Qdrant MCP Server 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 delete_documents? +

Register the Qdrant MCP Server MCP server in PolicyLayer and add a rule for delete_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 Qdrant MCP Server. Nothing to install.

What risk level is delete_documents? +

delete_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 delete_documents? +

Yes. Add a rate_limit block to the delete_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 delete_documents completely? +

Set action: deny in the PolicyLayer policy for delete_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 delete_documents? +

delete_documents is provided by the Qdrant MCP Server MCP server (mhalder/qdrant-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Qdrant MCP Server tool call.

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

CHECK YOUR STACK →