AI agents call get_bitbucket_pr_diff to retrieve information from Bitbucket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves pull request diff information for review purposes. This is a read-only operation that accesses existing data (code changes in a PR) without creating, modifying, deleting, or executing anything. The 'get_' prefix and lack of any write/execute/delete keywords indicate passive data retrieval.
From the tool's definition Tool name 'get_bitbucket_pr_diff' indicates retrieval of pull request diff/comparison data. Server context shows this is for code review, suggesting the tool reads and displays PR changes without modifying them.
Attacks that exploit this kind of access
get_bitbucket_pr_diff. It is categorised as a Read tool in the Bitbucket MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket MCP server in PolicyLayer and add a rule for get_bitbucket_pr_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. Nothing to install.
get_bitbucket_pr_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_bitbucket_pr_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_bitbucket_pr_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_bitbucket_pr_diff is provided by the Bitbucket MCP server (jishadmt/bitbucket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_bitbucket_pr_diff is one line of Bitbucket's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →