delete_by_source
Delete all documents from a specific source.
This record as markdown: /tools/0xrdan-mcp-rag-server/delete-by-source.md
What delete_by_source does on MCP RAG Server
AI agents call delete_by_source to permanently remove resources in MCP RAG Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_by_source is rated Critical
This tool permanently removes all documents associated with a given source from the knowledge base. Deletion is irreversible and cannot be undone through normal operations, making it Destructive rather than Write. The blast radius is high: an AI agent with access to this tool could wipe out entire sections of a knowledge base if it misidentifies or is tricked into targeting the wrong source.
From the tool's definition Tool name 'delete_by_source' combined with description 'Delete all documents from a specific source' — uses imperative 'delete' indicating irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_by_source safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP RAG Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_by_source, this is the rule to start with:
delete_by_source is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP RAG Server, apply this rule, and every delete_by_source call is checked against it from then on.
Questions about delete_by_source
Delete all documents from a specific source. It is categorised as a Destructive tool in the MCP RAG Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP RAG Server MCP server in PolicyLayer and add a rule for delete_by_source: 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 Server. Nothing to install.
delete_by_source 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_by_source 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_by_source. 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_by_source is provided by the MCP RAG Server MCP server (0xrdan/mcp-rag-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP RAG Server, and thousands of servers like it.
Across the catalogue