Remove specific documentation sources from the system by their URLs. Use this tool to clean up outdated documentation, remove incorrect sources, or manage the documentation collection. The removal is permanent and will affect future search results. Supports removing multiple URLs in a single oper...
AI agents call remove_documentation to permanently remove resources in RAG Documentation MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the tool removes documentation rather than user data, the removal is permanent and irreversible, affecting the system's knowledge base and future search results. An AI agent misusing this tool could permanently delete critical documentation sources.
From the tool's definition Tool description states: 'Remove specific documentation sources from the system by their URLs' and 'The removal is permanent and will affect future search results.' The explicit mention of permanence and irreversibility, combined with 'Supports removing…
Attacks that exploit this kind of access
Remove specific documentation sources from the system by their URLs. Use this tool to clean up outdated documentation, remove incorrect sources, or manage the documentation collection. The removal is permanent and will affect future search results. Supports removing multiple URLs in a single operation. It is categorised as a Destructive tool in the RAG Documentation MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RAG Documentation MCP Server MCP server in PolicyLayer and add a rule for remove_documentation: 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 RAG Documentation MCP Server. Nothing to install.
remove_documentation 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_documentation 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_documentation. 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_documentation is provided by the RAG Documentation MCP Server MCP server (jumasheff/mcp-ragdoc-fork). 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 →