Get a single branch restriction by its ID.
AI agents call get_branch_restriction 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 retrieves information about a branch restriction (a read-only query operation). It takes a branch restriction ID as input and returns details about that restriction. There are no side effects, no data modifications, no code execution, and no destructive operations. This is a straightforward information retrieval action, fitting the 'Read' category.
From the tool's definition Tool name 'get_branch_restriction' and description 'Get a single branch restriction by its ID' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get a single branch restriction by its ID. 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 get_branch_restriction: 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.
get_branch_restriction 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_branch_restriction 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_branch_restriction. 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_branch_restriction 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 →