delete_document

Delete a specific document by ID

SERVERDaniel LightRAG MCP Server SOURCEdesimpkins/daniel-lightrag-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/desimpkins-daniel-lightrag-mcp/delete-document.md

WHAT IT DOES

What delete_document does on Daniel LightRAG MCP Server

AI agents call delete_document to permanently remove resources in Daniel LightRAG MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_document is rated Critical

Deleting a document by ID is an irreversible operation that removes stored data. In a RAG (Retrieval-Augmented Generation) system, this also likely affects the knowledge graph and embeddings derived from that document, amplifying the blast radius beyond a simple record deletion.

From the tool's definition 'Delete a specific document by ID' — permanently removes a document from the system

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_document safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Daniel LightRAG MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_document, this is the rule to start with:

delete_document Hidden

delete_document is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Daniel LightRAG MCP Server, apply this rule, and every delete_document call is checked against it from then on.

FAQ

Questions about delete_document

What does the delete_document tool do? +

Delete a specific document by ID. It is categorised as a Destructive tool in the Daniel LightRAG 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? +

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

What risk level is delete_document? +

delete_document 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? +

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

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

delete_document is provided by the Daniel LightRAG MCP Server MCP server (desimpkins/daniel-lightrag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Daniel LightRAG MCP Server, and thousands of servers like it.

This server

All 21 Daniel LightRAG MCP Server tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →