bitbucket_merge_pr

Merge a pull request

SERVERContextForge MCP Gateway SOURCEjrmatherly/mcp-context-forge

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jrmatherly-mcp-context-forge/bitbucket-merge-pr.md

WHAT IT DOES

What bitbucket_merge_pr does on ContextForge MCP Gateway

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

RISK

Why bitbucket_merge_pr is rated Medium

Merging a pull request integrates code changes into a target branch. While this modifies repository state, it is technically reversible (the merge commit can be reverted), so it falls under Write rather than Destructive.

From the tool's definition Merge a pull request

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bitbucket_merge_pr safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bitbucket_merge_pr, this is the rule to start with:

bitbucket_merge_pr Rate-limited

bitbucket_merge_pr 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": {
    "bitbucket_merge_pr": {
      "limits": [
        {
          "counter": "bitbucket_merge_pr_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every bitbucket_merge_pr call is checked against it from then on.

FAQ

Questions about bitbucket_merge_pr

What does the bitbucket_merge_pr tool do? +

Merge a pull request. It is categorised as a Write tool in the ContextForge MCP Gateway 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_pr? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for bitbucket_merge_pr: 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 ContextForge MCP Gateway. Nothing to install.

What risk level is bitbucket_merge_pr? +

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

Can I rate-limit bitbucket_merge_pr? +

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

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

bitbucket_merge_pr is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ContextForge MCP Gateway, and thousands of servers like it.

This server

All 221 ContextForge MCP Gateway tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →