Delete a branch restriction.
AI agents call delete_branch_restriction to permanently remove resources in Bitbucket — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Branch restrictions are security controls that enforce merge rules, approval requirements, and deployment policies. Deleting a branch restriction removes those protections permanently and cannot be undone without recreating the rule. This is a destructive action that could allow unauthorized code to be merged or deployed.
From the tool's definition Tool name is 'delete_branch_restriction' and description states 'Delete a branch restriction.' The verb 'delete' combined with 'restriction' indicates irreversible removal of a branch protection rule.
Attacks that exploit this kind of access
Delete a branch restriction. It is categorised as a Destructive tool in the Bitbucket MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bitbucket MCP server in PolicyLayer and add a rule for delete_branch_restriction: 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. Nothing to install.
delete_branch_restriction 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_restriction 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_restriction. 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_restriction is provided by the Bitbucket MCP server (javimaligno/mcp-server-bitbucket). 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 →