delete_repository
AI agents call delete_repository to permanently remove resources in Bitbucket Server MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a repository is irreversible and eliminates all associated data, branches, commits, and history. This has severe blast radius if triggered by an AI agent on the wrong repository or by mistake. Despite the empty description, the action conveyed by the name and the server's own characterization of deletion operations as opt-in justifies the Destructive category and high severity.
From the tool's definition Tool name: 'delete_repository' — 'delete' indicates irreversible removal. The server description states 'opt-in deletion operations', confirming this tool performs destructive actions.
Attacks that exploit this kind of access
delete_repository. It is categorised as a Destructive tool in the Bitbucket Server MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bitbucket 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 Bitbucket Server MCP. Nothing to install.
delete_repository 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_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.
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.
delete_repository is provided by the Bitbucket Server MCP server (manpreetshuann/bitbucket-server-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 →