Get details of a Bitbucket pull request including merge commit information
AI agents call get_pull_request 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 query operation that returns pull request metadata and status information. There are no side effects—it does not create, modify, delete, execute code, or trigger external operations. The data retrieved is informational only, making this a straightforward Read category tool with low severity since viewing pull request details poses minimal risk even if accessed by an unauthorized agent.
From the tool's definition The tool 'get_pull_request' retrieves details of a pull request including merge commit information. The verb 'get' and the action of retrieving data without modification confirm this is a read operation.
Attacks that exploit this kind of access
Get details of a Bitbucket pull request including merge commit information. 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_pull_request: 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_pull_request 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_pull_request 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_pull_request. 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_pull_request is provided by the Bitbucket MCP Server MCP server (zhanglc/bitbucket-mcp-server). 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 →