bitbucket_merge_pull_request

THE RISK

Medium Risk

Why bitbucket_merge_pull_request needs a policy

Merging a pull request modifies the repository state by updating a branch with new commits. This is a reversible write operation (the merge can be reverted via revert commits), not destructive. However, it has high severity because an AI agent misusing this could merge unreviewed or malicious code into production branches, affecting code integrity and potentially causing system failures.

From the tool's definition Tool name is 'bitbucket_merge_pull_request' and description states it 'Merges a Bitbucket pull request'. Merging is a write operation that modifies the target branch by integrating code changes.

Documented attack patterns abuse exactly the kind of access bitbucket_merge_pull_request gives an agent:

POLICY

How to control bitbucket_merge_pull_request

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Bitbucket, and nothing reaches the server without passing your rules. This is the rule we recommend for bitbucket_merge_pull_request:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bitbucket_merge_pull_request": {
      "limits": [
        {
          "counter": "bitbucket_merge_pull_request_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

bitbucket_merge_pull_request stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Mcp Bitbucket — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mcp Bitbucket tools

Write bitbucket_decline_pull_request Declines a Bitbucket pull request Write bitbucket_add_pull_request_comment Adds a general comment to a Bitbucket pull request Write bitbucket_add_pull_request_file_line_comment Adds a comment to a Bitbucket pull request, optionally as an inline comment on a specific Write bitbucket_approve_pull_request Approves a Bitbucket pull request Write bitbucket_create_branch Creates a new branch in a Bitbucket repository. Write bitbucket_create_pull_request Creates a new Bitbucket pull request Read bitbucket_browse_directory Browses a directory in a Bitbucket repository. Read bitbucket_get_file_content Gets the content of a specific file from a Bitbucket repository.

All 18 Mcp Bitbucket tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about bitbucket_merge_pull_request

What does the bitbucket_merge_pull_request tool do? +

Merges a Bitbucket pull request. It is categorised as a Write tool in the Mcp Bitbucket MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bitbucket_merge_pull_request? +

Register the Mcp Bitbucket MCP server in PolicyLayer and add a rule for bitbucket_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 Mcp Bitbucket. Nothing to install.

What risk level is bitbucket_merge_pull_request? +

bitbucket_merge_pull_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bitbucket_merge_pull_request? +

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

How do I block bitbucket_merge_pull_request completely? +

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

What MCP server provides bitbucket_merge_pull_request? +

bitbucket_merge_pull_request is provided by the Mcp Bitbucket MCP server (n11techhub/mcp-bitbucket). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Bitbucket tool call.

Start from Mcp Bitbucket, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →