Retrieve full details for a pull request including title, description, author, state, source branch (fromRef), destination branch (toRef), created/updated dates, reviewers, and participants. Use this to get comprehensive PR metadata.
AI agents call get_pull_request to retrieve information from Mcp Bitbucket Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pull request metadata without creating, modifying, or deleting any data. It has no side effects and presents no risk of unintended data loss or operational harm. The blast radius is limited to information disclosure of PR details that would typically be accessible to authenticated users.
From the tool's definition Tool name is 'get_pull_request' and description states it 'Retrieve[s] full details for a pull request' with no modification or deletion capability mentioned. The action is purely informational: 'get comprehensive PR metadata'.
Attacks that exploit this kind of access
Retrieve full details for a pull request including title, description, author, state, source branch (fromRef), destination branch (toRef), created/updated dates, reviewers, and participants. Use this to get comprehensive PR metadata. It is categorised as a Read tool in the Mcp Bitbucket Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bitbucket 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 Mcp Bitbucket 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 Mcp Bitbucket Server MCP server (mcp-bitbucket-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 →