delete_branch
AI agents call delete_branch 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 branch removes version control history and references irreversibly. While not as critical as deleting entire repositories, branch deletion can disrupt collaboration, lose work if the branch contained unmerged commits, and cannot be easily undone by typical users. This is categorized as Destructive rather than Write because the operation cannot be reversed without access to reflog or backups.
From the tool's definition Tool name is 'delete_branch' with an empty description. The verb 'delete' combined with the object 'branch' indicates irreversible deletion of a git branch.
Attacks that exploit this kind of access
delete_branch. 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_branch: 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_branch 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_branch 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_branch. 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_branch 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 →