Remove a specific document from the index by file path
AI agents call remove_document to permanently remove resources in Mcp Rag — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes document data from the RAG index. While not a financial transaction or arbitrary code execution, the removal is irreversible and constitutes data destruction. If an AI agent misuses this tool with an incorrect or malicious file path, critical indexed documents could be lost without recovery.
From the tool's definition Tool name 'remove_document' and description 'Remove a specific document from the index by file path' — uses destructive verb 'Remove' and irreversibly deletes indexed document data.
Documented attack patterns abuse exactly the kind of access remove_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_document:
{
"version": "1",
"default": "deny",
"hide": [
"remove_document"
]
}remove_document 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.
Remove a specific document from the index by file path. It is categorised as a Destructive tool in the Mcp Rag MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Rag MCP server in PolicyLayer and add a rule for remove_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. Nothing to install.
remove_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 remove_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 remove_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.
remove_document is provided by the Mcp Rag MCP server (kwanleefrmvi/mcp-rag-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Rag, 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.
5 Mcp Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.