List branches in a Bitbucket repository
AI agents call bb_list_branches to retrieve information from Bitbucket Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns branch information from a repository without creating, modifying, deleting, or executing any operations. It is purely informational and has no capability to alter state or trigger external actions. Misuse would only expose repository structure information, which has minimal security impact.
From the tool's definition Tool name 'bb_list_branches' and description 'List branches in a Bitbucket repository' indicate a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
List branches in a Bitbucket repository. It is categorised as a Read tool in the Bitbucket Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket Cloud MCP Server MCP server in PolicyLayer and add a rule for bb_list_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 Cloud MCP Server. Nothing to install.
bb_list_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 bb_list_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 bb_list_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.
bb_list_branches is provided by the Bitbucket Cloud MCP Server MCP server (or2ooo/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 →