delete_document_by_id

THE RISK

Critical Risk

Why delete_document_by_id needs a policy

The tool permanently removes data (a document) from a search index using its ID. Deletion is irreversible and cannot be undone, placing it in the Destructive category. Severity is high because an AI agent with access to this tool could maliciously or accidentally delete important indexed documents, and the blast radius depends on what data is in the index and whether backups exist.

From the tool's definition Tool name contains 'delete_document_by_id' and description states 'Delete a single document from an index' — this is an irreversible deletion operation.

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

POLICY

How to control delete_document_by_id

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

policy.json

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

delete_document_by_id 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 Searchcraft 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 Searchcraft MCP Server tools

Destructive delete_all_documents Delete all documents from an index. The index will continue to exist after all documents a Destructive delete_all_keys Delete all authentication keys on the Searchcraft cluster. Use with extreme caution! Destructive delete_all_stopwords Delete all custom stopwords from an index. This only affects custom stopwords, not the def Destructive delete_all_synonyms Delete all synonyms from an index. Destructive delete_documents_by_field Delete one or several documents from an index by field term match (e.g., {id: Destructive delete_documents_by_query Delete one or several documents from an index by query match. Destructive delete_federation Delete a federation permanently. Destructive delete_index Delete an index and all its documents permanently.

All 48 Searchcraft 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 Searchcraft 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_document_by_id

What does the delete_document_by_id tool do? +

Delete a single document from an index by its internal Searchcraft ID (_id). It is categorised as a Destructive tool in the Searchcraft 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_document_by_id? +

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

What risk level is delete_document_by_id? +

delete_document_by_id 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_document_by_id? +

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

Set action: deny in the PolicyLayer policy for delete_document_by_id. 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_document_by_id? +

delete_document_by_id is provided by the Searchcraft MCP Server MCP server (searchcraft-inc/searchcraft-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 Searchcraft MCP Server tool call.

Start from Searchcraft 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 →