Delete all knowledge base data associated with a specific repository ID. This removes all scanned files, chunks, and embeddings for that repository.
AI agents call knowledge_delete_repo to permanently remove resources in Knowledge MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently and irreversibly deletes all knowledge base data for a repository—scanned files, chunks, and embeddings cannot be recovered without a complete re-scan. While not directly destructive to production systems, it represents irreversible loss of indexed information.
From the tool's definition Tool description states it "Delete[s] all knowledge base data associated with a specific repository ID. This removes all scanned files, chunks, and embeddings for that repository." The use of "delete" and "removes all" indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete all knowledge base data associated with a specific repository ID. This removes all scanned files, chunks, and embeddings for that repository. It is categorised as a Destructive tool in the Knowledge MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Knowledge MCP server in PolicyLayer and add a rule for knowledge_delete_repo: 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 MCP. Nothing to install.
knowledge_delete_repo 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 knowledge_delete_repo 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 knowledge_delete_repo. 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.
knowledge_delete_repo is provided by the Knowledge MCP server (paulthesecond/knowledgebase-mcp). 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 →