remove_repository

THE RISK

Critical Risk

Why remove_repository needs a policy

Removing a repository from tracking is a destructive action that permanently stops analysis and monitoring of that codebase within the system. This results in loss of indexed data, analysis history, and tracking state—effects that cannot be reversed without re-adding and re-analyzing the repository. While not directly deleting source code, it irreversibly removes the repository from the server's tracking system.

From the tool's definition Tool name 'remove_repository' and description 'Remove a repository from tracking' indicate irreversible deletion of tracked repository data. The verb 'remove' combined with the finality of ceasing to track a repository suggests data loss that cannot be undone.

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

POLICY

How to control remove_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 remove_repository:

policy.json

{
  "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.

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Code Analysis Server tools

Destructive delete_repository Delete a repository and all its data Execute sync_repository Manually trigger sync for a specific repository Write add_repository Add a new repository to track Write update_embeddings Update embeddings for a repository Write update_repository Update repository metadata Write update_repository_settings Update repository settings Read analyze_bounded_context Analyze a bounded context and its relationships Read analyze_coupling Analyze coupling between bounded contexts with metrics and recommendations

All 44 MCP Code Analysis Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MCP Code Analysis Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_repository

What does the remove_repository tool do? +

Remove a repository from tracking. 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 remove_repository? +

Register the MCP Code Analysis 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 MCP Code Analysis Server. Nothing to install.

What risk level is remove_repository? +

remove_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 remove_repository? +

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.

How do I block remove_repository completely? +

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.

What MCP server provides remove_repository? +

remove_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.

CHECK YOUR STACK →