Critical Risk →

bb_delete_repository

Delete a repository from Bitbucket

How to control bb_delete_repository ↓

What bb_delete_repository does on MCP Bitbucket Python

AI agents call bb_delete_repository to permanently remove resources in MCP Bitbucket Python — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why bb_delete_repository needs a policy

Repository deletion cannot be undone and results in permanent loss of all code, history, issues, and pull requests. This is the most severe action on the Bitbucket server and matches the Destructive category definition of irreversibly deleting data. Critical severity is appropriate given the scale of potential data loss.

From the tool's definition Tool name 'bb_delete_repository' explicitly states deletion action; description confirms 'Delete a repository from Bitbucket' — this irreversibly removes an entire repository and all its contents.

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

How to control bb_delete_repository

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

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

bb_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 Bitbucket Python — 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 bb_delete_repository

What does the bb_delete_repository tool do? +

Delete a repository from Bitbucket. It is categorised as a Destructive tool in the MCP Bitbucket Python 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 bb_delete_repository? +

Register the MCP Bitbucket Python MCP server in PolicyLayer and add a rule for bb_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 Bitbucket Python. Nothing to install.

What risk level is bb_delete_repository? +

bb_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 bb_delete_repository? +

Yes. Add a rate_limit block to the bb_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 bb_delete_repository completely? +

Set action: deny in the PolicyLayer policy for bb_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 bb_delete_repository? +

bb_delete_repository is provided by the MCP Bitbucket Python MCP server (kallows/mcp-bitbucket). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Bitbucket Python tool call.

Start from MCP Bitbucket Python, 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.

10 MCP Bitbucket Python 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.