Add a comment to a pull request. Supports: 1) General PR comments, 2) Replies to existing comments, 3) Inline comments on specific code lines (using line_number OR code_snippet), 4) Code suggestions for single or multi-line replacements. For inline comments, you can either provide exact line_numb...
AI agents use add_comment to create or update resources in Bitbucket MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitbucket MCP Server environment.
This tool creates new comment records on pull requests, which is a reversible write operation (comments can be edited or deleted). It does not execute code, delete data, move money, or trigger external systems—it only adds metadata/discussion content to a PR.
From the tool's definition Tool description explicitly states 'Add a comment' and supports creating 'General PR comments', 'Replies to existing comments', and 'Inline comments'. These are write operations that modify pull request state by creating new comment data.
Attacks that exploit this kind of access
Add a comment to a pull request. Supports: 1) General PR comments, 2) Replies to existing comments, 3) Inline comments on specific code lines (using line_number OR code_snippet), 4) Code suggestions for single or multi-line replacements. For inline comments, you can either provide exact line_number or use code_snippet to auto-detect the line. It is categorised as a Write tool in the Bitbucket MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitbucket MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_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 add_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 add_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.
add_comment is provided by the Bitbucket MCP Server MCP server (zhanglc/bitbucket-mcp-server). 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 →