Add a comment to a pull request (general, inline, or a threaded reply to another comment)
AI agents use addPullRequestComment to create or update resources in Bitbucket MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitbucket MCP environment.
Adding a comment creates and persists new data in Bitbucket, making it a Write operation. It is not Read (no data retrieval), Execute (no code/scripts run), Destructive (reversible), Financial, or Other. Severity is medium because while comment spam or misleading comments could disrupt workflows, the blast radius is limited to a single pull request and comments remain auditable/removable.
From the tool's definition Tool performs 'Add a comment' action, which creates new data (a comment) in the pull request system. This is a reversible modification—comments can be deleted via the deletePullRequestComment tool also present on this server.
Documented attack patterns abuse exactly the kind of access addPullRequestComment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitbucket MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for addPullRequestComment:
{
"version": "1",
"default": "deny",
"tools": {
"addPullRequestComment": {
"limits": [
{
"counter": "addpullrequestcomment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}addPullRequestComment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a comment to a pull request (general, inline, or a threaded reply to another comment). It is categorised as a Write tool in the Bitbucket MCP 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 addPullRequestComment: 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. Nothing to install.
addPullRequestComment 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 addPullRequestComment 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 addPullRequestComment. 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.
addPullRequestComment is provided by the Bitbucket MCP server (matanyemini/bitbucket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bitbucket MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
49 Bitbucket MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.