List all branch restrictions for a repository.
AI agents call list_branch_restrictions 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 queries and retrieves existing branch restriction policies without creating, modifying, deleting, or executing any changes. It is purely informational, fitting the Read category. Severity is low because disclosure of branch restriction metadata poses minimal risk—an AI agent simply learns what protections exist on branches, which does not enable unauthorized access or actions.
From the tool's definition Tool name 'list_branch_restrictions' and description 'List all branch restrictions for a repository' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List all branch restrictions for a repository. 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 list_branch_restrictions: 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.
list_branch_restrictions 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 list_branch_restrictions 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 list_branch_restrictions. 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.
list_branch_restrictions is provided by the Bitbucket MCP Server MCP server (korfu/mcp-bitbucket). 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 →