bb_decline_pull_request

Decline a pull request (destructive action, requires confirmation)

Server Bitbucket Cloud MCP Server or2ooo/bitbucket-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What bb_decline_pull_request does on Bitbucket Cloud MCP Server

AI agents call bb_decline_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.

Why bb_decline_pull_request needs a policy

Declining a pull request is explicitly labeled as a destructive action. While it does not delete data outright, declining a PR is typically irreversible in workflow terms — it closes the PR and rejects the proposed changes, requiring the author to reopen or create a new PR. The server itself flags this as destructive and requires confirmation, indicating high blast radius if misused by an AI agent.

From the tool's definition 'Decline a pull request (destructive action, requires confirmation)'

Questions about bb_decline_pull_request

What does the bb_decline_pull_request tool do? +

Decline 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.

How do I enforce a policy on bb_decline_pull_request? +

Register the Bitbucket Cloud MCP Server MCP server in PolicyLayer and add a rule for bb_decline_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.

What risk level is bb_decline_pull_request? +

bb_decline_pull_request is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit bb_decline_pull_request? +

Yes. Add a rate_limit block to the bb_decline_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.

How do I block bb_decline_pull_request completely? +

Set action: deny in the PolicyLayer policy for bb_decline_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.

What MCP server provides bb_decline_pull_request? +

bb_decline_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.