get_pull_request_diff_stat
AI agents call get_pull_request_diff_stat to retrieve information from Bitbucket Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diff statistics for a pull request, which is a read operation that queries existing data without modifying, executing, or deleting anything. The blast radius of misuse is minimal—an agent could only access diff statistics it shouldn't see, not cause irreversible changes or execute code.
From the tool's definition Tool name 'get_pull_request_diff_stat' indicates retrieval of pull request diff statistics. The 'get_' prefix and 'diff_stat' (statistics about differences) are characteristic of read-only query operations.
Attacks that exploit this kind of access
get_pull_request_diff_stat. It is categorised as a Read tool in the Bitbucket Server MCP MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket Server MCP server in PolicyLayer and add a rule for get_pull_request_diff_stat: 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 Server MCP. Nothing to install.
get_pull_request_diff_stat 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_stat 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_stat. 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_stat is provided by the Bitbucket Server MCP server (manpreetshuann/bitbucket-server-mcp). 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 →