AI agents call remove_file to permanently remove resources in Local Rag — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a file from the semantic search index without reversibility. If an AI agent is given uncontrolled access and calls this with user-controlled file paths, it could remove critical code files from the searchable knowledge base, disrupting RAG functionality and potentially hiding important context.
From the tool's definition Tool name 'remove_file' and description 'Remove a specific file from the RAG index' indicate irreversible deletion of indexed data.
Documented attack patterns abuse exactly the kind of access remove_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Local Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_file:
{
"version": "1",
"default": "deny",
"hide": [
"remove_file"
]
}remove_file 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 file from the RAG index. It is categorised as a Destructive tool in the Local Rag MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Local Rag MCP server in PolicyLayer and add a rule for remove_file: 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 Local Rag. Nothing to install.
remove_file 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_file 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_file. 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_file is provided by the Local Rag MCP server (thewinci/mimirs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Local 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.
29 Local Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.