Add a comment to a pull request, optionally as an inline comment on a specific file and line. Use parent_id to create a threaded reply to an existing comment.
AI agents use bb_add_pull_request_comment to create or update resources in Bitbucket Cloud MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitbucket Cloud MCP Server environment.
Adding comments creates reversible new data in the pull request system. While it modifies state, it does not execute code, delete data, move money, or trigger destructive operations. The blast radius is medium because malicious comments could spread misinformation or spam across pull requests, but the effect is containable and reversible. This is clearly a Write-category tool.
From the tool's definition Tool description states it 'Add a comment to a pull request' and supports threaded replies via parent_id. These are write operations that create new content (comments) in the repository collaboration system.
Attacks that exploit this kind of access
Add a comment to a pull request, optionally as an inline comment on a specific file and line. Use parent_id to create a threaded reply to an existing comment. It is categorised as a Write tool in the Bitbucket Cloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitbucket Cloud MCP Server MCP server in PolicyLayer and add a rule for bb_add_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 Cloud MCP Server. Nothing to install.
bb_add_pull_request_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bb_add_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 bb_add_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.
bb_add_pull_request_comment is provided by the Bitbucket Cloud MCP Server MCP server (or2ooo/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 →