Low Risk

getPullRequestPatch

Get patch for a pull request

How to control getPullRequestPatch ↓

What getPullRequestPatch does on Bitbucket MCP

AI agents call getPullRequestPatch to retrieve information from Bitbucket MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why getPullRequestPatch needs a policy

This tool retrieves or queries data (a patch/diff) from an existing pull request without modifying, deleting, or executing anything. It is purely informational and non-mutative, fitting the Read category with low severity since the blast radius of misuse is minimal—an AI agent can only view patch data it is already authorized to access.

From the tool's definition Tool name 'getPullRequestPatch' and description 'Get patch for a pull request' indicate a retrieval operation. A patch is a read-only representation of code changes; fetching it has no side effects.

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

How to control getPullRequestPatch

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getPullRequestPatch": {}
  }
}

getPullRequestPatch is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about getPullRequestPatch

What does the getPullRequestPatch tool do? +

Get patch for a pull request. It is categorised as a Read tool in the Bitbucket MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getPullRequestPatch? +

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

What risk level is getPullRequestPatch? +

getPullRequestPatch is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getPullRequestPatch? +

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

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

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

Enforce policy on every Bitbucket MCP tool call.

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

Free to start. No card required.

49 Bitbucket MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.