Remove a document from the knowledge base index. Mutating — removes index entries. If delete_file=True, also permanently deletes the file from disk (irreversible, cannot be undone). Args: filepath: Path to the document file. Must be an indexed document — use list_documents() to find valid paths. ...
AI agents call remove_document to permanently remove resources in Knowledge Rag — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the primary action of removing a document from the index could be considered Write (reversible modification), the optional delete_file parameter enables permanent, irreversible deletion of files from disk. This irreversible destruction capability elevates the tool to Destructive severity.
From the tool's definition Tool description explicitly states it 'permanently deletes the file from disk (irreversible, cannot be undone)' when delete_file=True. The mutating nature and irreversible file deletion capability places this in the Destructive category.
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 Knowledge 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 document from the knowledge base index. Mutating — removes index entries. If delete_file=True, also permanently deletes the file from disk (irreversible, cannot be undone). Args: filepath: Path to the document file. Must be an indexed document — use list_documents() to find valid paths. delete_file: If True, permanently deletes the file from disk in addition to removing from the index (default: False). Returns: JSON string with removal results (filepath, status). Usage: Use to unindex a document while keeping the file on disk (default). Set delete_file=True only for permanent removal. Use update_document() to replace content instead of removing. Use reindex_documents(force=True) if you deleted the file manually on disk outside of this tool. It is categorised as a Destructive tool in the Knowledge Rag MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Knowledge 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 Knowledge 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 Knowledge Rag MCP server (lyonzin/knowledge-rag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Knowledge 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.
12 Knowledge Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.