add_pr_comment · Bitbucket Cloud MCP Server MCP

WHAT IT DOES

What add_pr_comment does on Bitbucket Cloud MCP Server

AI agents use add_pr_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.

WHY IT NEEDS A POLICY

Why add_pr_comment needs a policy

Adding comments to pull requests creates new data (comments) that are stored in Bitbucket and visible to collaborators. This is reversible (comments can be deleted) and has moderate blast radius if misused by an AI agent—it could spam PRs, post misleading information, or interfere with code review workflows. It does not execute code, delete data, or move money, so Write is the appropriate category.

From the tool's definition Tool description explicitly states 'Add a comment to a pull request' and 'Can be a general comment or an inline comment on a specific file/line.' This is content creation/modification on an existing resource.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_pr_comment Rate-limited

add_pr_comment 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_pr_comment": {
      "limits": [
        {
          "counter": "add_pr_comment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Bitbucket Cloud MCP Server, so you can run agents against it safely.

FAQ

Questions about add_pr_comment

What does the add_pr_comment tool do? +

Add a comment to a pull request. Can be a general comment or an inline comment on a specific file/line. 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.

How do I enforce a policy on add_pr_comment? +

Register the Bitbucket Cloud MCP Server 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 Cloud MCP Server. Nothing to install.

What risk level is add_pr_comment? +

add_pr_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_pr_comment? +

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.

How do I block add_pr_comment completely? +

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.

What MCP server provides add_pr_comment? +

add_pr_comment is provided by the Bitbucket Cloud MCP Server MCP server (lexmata/bitbucket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.