AI agents call list_pr_comments to retrieve information from Bitbucket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing pull request comments without creating, modifying, deleting, or executing anything. It is a pure read operation with minimal blast radius if misused by an AI agent—the worst outcome would be unauthorized information disclosure about PR review discussions, which is lower-impact than write, execute, or destructive operations.
From the tool's definition Tool name 'list_pr_comments' and description 'List all comments on a pull request... Returns comments sorted oldest-first' indicate retrieval and querying of comment data with no modification or side effects.
Attacks that exploit this kind of access
List all comments on a pull request, including general and inline (file+line) comments. Returns comments sorted oldest-first. It is categorised as a Read tool in the Bitbucket MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket MCP server in PolicyLayer and add a rule for list_pr_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. Nothing to install.
list_pr_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 list_pr_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 list_pr_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.
list_pr_comments is provided by the Bitbucket MCP server (jacobpixleratgather/bitbucket-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 →