add_pr_file_comment · Mcp Bitbucket Server MCP

WHAT IT DOES

What add_pr_file_comment does on Mcp Bitbucket Server

AI agents use add_pr_file_comment to create or update resources in Mcp Bitbucket Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Bitbucket Server environment.

WHY IT NEEDS A POLICY

Why add_pr_file_comment needs a policy

This tool creates new comment data within a pull request, a reversible write operation. It has a medium severity because while comments can be deleted (via delete_pr_comment shown in sibling tools), they create visible artifacts in code review workflows that could be misleading, spam-like, or interfere with development processes if abused by an AI agent.

From the tool's definition add_pr_file_comment adds a comment to a pull request; the description states it will 'appear at the file level in the PR diff view', which creates new data that modifies the PR record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_pr_file_comment Rate-limited

add_pr_file_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_file_comment": {
      "limits": [
        {
          "counter": "add_pr_file_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 Mcp Bitbucket Server, so you can run agents against it safely.

FAQ

Questions about add_pr_file_comment

What does the add_pr_file_comment tool do? +

Add a comment attached to a specific file in a pull request (not to a specific line). The comment will appear at the file level in the PR diff view. To reply to an existing comment (including file/line comments), use add_pr_comment instead. It is categorised as a Write tool in the Mcp Bitbucket 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_file_comment? +

Register the Mcp Bitbucket Server MCP server in PolicyLayer and add a rule for add_pr_file_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 Mcp Bitbucket Server. Nothing to install.

What risk level is add_pr_file_comment? +

add_pr_file_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_file_comment? +

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

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

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