Delete document by ID from knowledge graph.
AI agents call delete_data to permanently remove resources in RAG-Anything MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes documents from the knowledge graph storage. Deletion cannot be undone without external backup/recovery mechanisms, making it a destructive operation. The severity is high because mistaken or malicious deletion of knowledge graph documents could cause significant data loss and impact downstream RAG functionality that depends on that ingested knowledge.
From the tool's definition Tool name is 'delete_data' and description states 'Delete document by ID from knowledge graph.' The verb 'Delete' combined with the action of removing data from a knowledge graph indicates irreversible removal.
Documented attack patterns abuse exactly the kind of access delete_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RAG-Anything MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_data:
{
"version": "1",
"default": "deny",
"hide": [
"delete_data"
]
}delete_data disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete document by ID from knowledge graph. It is categorised as a Destructive tool in the RAG-Anything MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RAG-Anything MCP Server MCP server in PolicyLayer and add a rule for delete_data: 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 RAG-Anything MCP Server. Nothing to install.
delete_data 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 delete_data 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 delete_data. 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.
delete_data is provided by the RAG-Anything MCP Server MCP server (serkanyasr/rag-anythink-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RAG-Anything MCP Server, 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.
8 RAG-Anything MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.