Compare two branches
AI agents call compare_branches 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 performs a read-only comparison operation. It retrieves and displays branch differences but does not create, modify, delete, or execute any code. Comparing branches is a standard code review operation with no side effects or destructive potential. The blast radius of misuse is minimal—an agent could only waste time or retrieve information already accessible through normal repository access.
From the tool's definition Tool name 'compare_branches' and description 'Compare two branches' indicate a query/retrieval operation that retrieves and displays differences between branches without modifying any repository state.
Attacks that exploit this kind of access
Compare two branches. 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 compare_branches: 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.
compare_branches 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 compare_branches 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 compare_branches. 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.
compare_branches is provided by the Bitbucket MCP Server MCP server (jlromano/bitbucket-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 →