merge_pull_request · Bitbucket MCP Server MCP: Risk & Policy

WHAT IT DOES

What merge_pull_request does on Bitbucket MCP Server

AI agents use merge_pull_request to create or update resources in Bitbucket MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitbucket MCP Server environment.

WHY IT NEEDS A POLICY

Why merge_pull_request needs a policy

Merging a pull request creates new commit history and updates branch references, which are reversible operations. While merging has significant blast radius (can introduce bugs, break builds, affect multiple team members), it is not irreversible like a delete or force-push. The high severity reflects the potential impact on codebase stability and deployment pipelines when misused by an AI agent.

From the tool's definition Tool name 'merge_pull_request' and description 'Merge a pull request' indicate the tool performs a merge operation, which modifies repository state by combining branches and is reversible (through revert commits), making it a Write operation rather than…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_pull_request Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Bitbucket MCP Server, so you can run agents against it safely.

FAQ

Questions about merge_pull_request

What does the merge_pull_request tool do? +

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

How do I enforce a policy on merge_pull_request? +

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

What risk level is merge_pull_request? +

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 merge_pull_request? +

Yes. Add a rate_limit block to the 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 merge_pull_request completely? +

Set action: deny in the PolicyLayer policy for 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 merge_pull_request? +

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