delete_repo
AI agents call delete_repo to permanently remove resources in Code Expert MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Despite the empty description, the tool name 'delete_repo' clearly indicates deletion of repository data, which is irreversible and cannot be undone. This fits the Destructive category. Severity is high because deleting a repository destroys all its contents, code history, and potentially impacts collaboration.
From the tool's definition Tool name is 'delete_repo' with an empty description. The name indicates irreversible deletion of repository data.
Attacks that exploit this kind of access
delete_repo. It is categorised as a Destructive tool in the Code Expert MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Code Expert MCP Server MCP server in PolicyLayer and add a rule for 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 Code Expert MCP Server. Nothing to install.
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 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 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.
delete_repo is provided by the Code Expert MCP Server MCP server (lfnovo/code-expert-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 →