Add a comment to an issue in a Bitbucket repository
AI agents use bb_comment_issue 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 a comment creates new data in the issue tracking system but is reversible (comments can be edited or deleted). This does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial). It is a standard write operation that modifies issue state by appending a comment, consistent with the Write category for create/update operations.
From the tool's definition Tool name 'bb_comment_issue' and description 'Add a comment to an issue' indicate creation of new comment data. The verb 'Add' and action of commenting represent reversible modification of issue state.
Attacks that exploit this kind of access
Add a comment to an issue in a Bitbucket repository. 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_comment_issue: 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_comment_issue 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_comment_issue 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_comment_issue. 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_comment_issue 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 →