Merge a pull request (destructive action, requires confirmation)
AI agents call bb_merge_pull_request to permanently remove resources in Bitbucket Cloud MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Merging a pull request irreversibly integrates code changes into the target branch. While the source branch still exists, the merge commit cannot be easily undone without force-pushing or revert commits, and it permanently alters the target branch history. The server itself classifies this as destructive and requires confirmation, supporting a high-severity Destructive classification.
From the tool's definition 'Merge a pull request (destructive action, requires confirmation)' — the description explicitly labels this a 'destructive action'
Attacks that exploit this kind of access
Merge a pull request (destructive action, requires confirmation). It is categorised as a Destructive tool in the Bitbucket Cloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bitbucket Cloud MCP Server MCP server in PolicyLayer and add a rule for bb_merge_pull_request: 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 Cloud MCP Server. Nothing to install.
bb_merge_pull_request 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 bb_merge_pull_request 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 bb_merge_pull_request. 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.
bb_merge_pull_request is provided by the Bitbucket Cloud MCP Server MCP server (or2ooo/bitbucket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
bb_merge_pull_request is one line of Bitbucket Cloud MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →