Remove a repository from the system by its name. This removes both the repository configuration and all indexed documents from the vector database.
AI agents call remove_repository 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.
The tool permanently deletes indexed documents and repository configuration from the vector database with no stated recovery mechanism. This is irreversible data loss, making it Destructive rather than Write.
From the tool's definition Tool description states it 'removes both the repository configuration and all indexed documents from the vector database' - irreversible deletion of indexed data.
Documented attack patterns abuse exactly the kind of access remove_repository gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RAG Documentation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_repository:
{
"version": "1",
"default": "deny",
"hide": [
"remove_repository"
]
}remove_repository 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 repository from the system by its name. This removes both the repository configuration and all indexed documents from the vector database. 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_repository: 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_repository 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_repository 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_repository. 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_repository is provided by the RAG Documentation MCP Server MCP server (rahulretnan/mcp-ragdocs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 RAG Documentation MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 RAG Documentation MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.