list_pull_request_comments
AI agents call list_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.
The 'list' prefix combined with the absence of any modification/deletion keywords and context from related tools suggests this retrieves or queries pull request comment data without side effects. This is a read-only operation with minimal security risk.
From the tool's definition Tool name 'list_pull_request_comments' indicates retrieval of pull request comments; no description provided but naming convention and context of sibling tools (add_pull_request_comment, approve_pull_request) confirm this is a query/list operation.
Attacks that exploit this kind of access
list_pull_request_comments. 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 list_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.
list_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 list_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 list_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.
list_pull_request_comments is provided by the Bitbucket Server MCP server (manpreetshuann/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 →