Delete a branch
AI agents call delete_branch to permanently remove resources in Bitbucket MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a branch is a destructive operation that permanently removes version control history from the accessible branch namespace. While the commits may still exist in the repository's object database if unreferenced, the branch reference itself is irreversibly deleted. This is more severe than Write (reversible modifications) or Execute (conditional operations).
From the tool's definition Tool name is 'delete_branch' with description 'Delete a branch'. The verb 'delete' explicitly indicates irreversible removal of a Git branch, which cannot be undone without access to reflog or repository backups.
Attacks that exploit this kind of access
Delete a branch. It is categorised as a Destructive tool in the Bitbucket MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bitbucket MCP 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 MCP Server. 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 MCP Server MCP server (zhanglc/bitbucket-mcp-server). 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 →