Get a single comment on a pull request by its ID.
AI agents call get_pull_request_comment 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 existing data (a pull request comment) without creating, modifying, deleting, or executing operations. It is a straightforward read-only query of repository metadata. The blast radius of misuse is minimal—an attacker could read comments but cannot alter them or trigger external actions.
From the tool's definition Tool name is 'get_pull_request_comment' and description states 'Get a single comment on a pull request by its ID' — the verb 'Get' and lack of any modification language indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a single comment on a pull request 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_pull_request_comment: 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_comment 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_comment 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_comment. 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_comment 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 →