Delete a document and its associated chunks
AI agents call delete_document to permanently remove resources in MCP RAG System — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion of documents and their vector embeddings/chunks from the RAG system. Once deleted, the data cannot be recovered through normal means. This is a destructive operation that cannot be undone, making it more severe than Write or Execute operations.
From the tool's definition The tool is named 'delete_document' and described as 'Delete a document and its associated chunks' — explicit use of 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a document and its associated chunks. It is categorised as a Destructive tool in the MCP RAG System MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP RAG System 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 MCP RAG System. Nothing to install.
delete_document 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_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.
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.
delete_document is provided by the MCP RAG System MCP server (nitin-kumar101/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →