AI agents use add_pr_comment to create or update resources in Bitbucket — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitbucket environment.
This tool creates new comments on pull requests, which modifies PR state reversibly (comments can be edited or deleted). It does not retrieve data (Read), execute arbitrary code (Execute), permanently destroy data (Destructive), or move money (Financial).
From the tool's definition Tool description states 'Post a general comment on a pull request', which is a create operation that adds new data to the PR discussion.
Attacks that exploit this kind of access
Post a general comment on a pull request (not tied to a specific file or line). For inline file/line comments, use. It is categorised as a Write tool in the Bitbucket MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitbucket MCP server in PolicyLayer and add a rule for add_pr_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. Nothing to install.
add_pr_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_pr_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_pr_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_pr_comment 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 →