Critical Risk →

delete_repository

Delete a repository and all its data

How to control delete_repository ↓

What delete_repository does on MCP Code Analysis Server

AI agents call delete_repository to permanently remove resources in MCP Code Analysis Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_repository needs a policy

This tool permanently removes a repository and all associated data without the ability to undo the action. This is a destructive operation with the highest severity due to complete data loss potential and the broad blast radius if misused by an AI agent (entire codebase erasure).

From the tool's definition Tool name is 'delete_repository' and description states 'Delete a repository and all its data' — explicitly irreversible deletion of data.

Documented attack patterns abuse exactly the kind of access delete_repository gives an agent:

How to control delete_repository

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Code Analysis Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_repository:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_repository"
  ]
}

delete_repository disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register MCP Code Analysis Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_repository

What does the delete_repository tool do? +

Delete a repository and all its data. It is categorised as a Destructive tool in the MCP Code Analysis Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_repository? +

Register the MCP Code Analysis Server MCP server in PolicyLayer and add a rule for delete_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 MCP Code Analysis Server. Nothing to install.

What risk level is delete_repository? +

delete_repository is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_repository? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_repository completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_repository? +

delete_repository is provided by the MCP Code Analysis Server MCP server (johannhartmann/mcpcodeanalysis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Code Analysis Server tool call.

Start from MCP Code Analysis Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

44 MCP Code Analysis Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.