Get all comments on a pull request
AI agents call get_pull_request_comments to retrieve information from Bitbucket Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing comments from a pull request without modifying, creating, deleting, or executing any operations. It is a straightforward read operation that queries data. The low severity reflects minimal blast radius—unauthorized access to PR comments could leak information but cannot alter code, delete resources, or trigger financial transactions.
From the tool's definition Tool name 'get_pull_request_comments' and description 'Get all comments on a pull request' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all comments on a pull request. It is categorised as a Read tool in the Bitbucket Server MCP MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket Server MCP server in PolicyLayer and add a rule for get_pull_request_comments: 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 Server MCP. Nothing to install.
get_pull_request_comments 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_comments 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_comments. 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_comments is provided by the Bitbucket Server MCP server (maniksi/bitbucket-server-mcp). 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 →