Get the diff/changes for a pull request with optional filtering
AI agents call get_pull_request_diff to retrieve information from Bitbucket MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays differences between code versions in a pull request. It is a read-only operation with no side effects—it does not modify repositories, execute code, delete data, or trigger external operations. The diff/changes are already committed to the pull request; viewing them causes no state changes. Lowest severity risk.
From the tool's definition Tool name is 'get_pull_request_diff' and description states 'Get the diff/changes for a pull request' - uses 'Get' verb indicating retrieval only, with 'optional filtering' suggesting query-like parameters.
Attacks that exploit this kind of access
Get the diff/changes for a pull request with optional filtering. It is categorised as a Read tool in the Bitbucket MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket MCP Server MCP server in PolicyLayer and add a rule for get_pull_request_diff: 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.
get_pull_request_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_pull_request_diff 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.
Set action: deny in the PolicyLayer policy for get_pull_request_diff. 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.
get_pull_request_diff 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.
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 →