add_pull_request_comment · Bitbucket MCP Server MCP

WHAT IT DOES

What add_pull_request_comment does on Bitbucket MCP Server

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

WHY IT NEEDS A POLICY

Why add_pull_request_comment needs a policy

This tool creates new data (pull request comments) that can be modified or deleted later, making it a Write operation rather than Read or Destructive. Severity is medium because comments on pull requests can influence code review decisions and team communication, but the effect is not irreversible (comments can be edited/deleted) and does not directly alter code or financial systems.

From the tool's definition Tool description states 'Add a comment to a pull request' which creates new comment data. Supports 'general comments, inline comments on specific files/lines, and replies to existing comments' - all are write operations that create new content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_pull_request_comment Rate-limited

add_pull_request_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_pull_request_comment": {
      "limits": [
        {
          "counter": "add_pull_request_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about add_pull_request_comment

What does the add_pull_request_comment tool do? +

Add a comment to a pull request. Supports general comments, inline comments on specific files/lines, and replies to existing comments. 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.

How do I enforce a policy on add_pull_request_comment? +

Register the Bitbucket MCP Server MCP server in PolicyLayer and add a rule for add_pull_request_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.

What risk level is add_pull_request_comment? +

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

Can I rate-limit add_pull_request_comment? +

Yes. Add a rate_limit block to the add_pull_request_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_pull_request_comment completely? +

Set action: deny in the PolicyLayer policy for add_pull_request_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_pull_request_comment? +

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