add_pr_inline_comment · Bitbucket MCP: Risk & Policy

WHAT IT DOES

What add_pr_inline_comment does on Bitbucket

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

WHY IT NEEDS A POLICY

Why add_pr_inline_comment needs a policy

This tool creates new comment data within Bitbucket, which is a reversible write operation. It does not execute code, delete data, or move funds. The severity is medium because malicious inline comments could obstruct code review workflows, introduce misinformation, or spam the PR, but the impact is limited to comment metadata and does not compromise the codebase itself.

From the tool's definition Tool name 'add_pr_inline_comment' and description 'Post a comment on a specific file and line within a pull request' explicitly indicate creation of a new comment artifact within a PR. The verb 'post' and 'add' confirm data creation/modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_pr_inline_comment Rate-limited

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

FAQ

Questions about add_pr_inline_comment

What does the add_pr_inline_comment tool do? +

Post a comment on a specific file and line within a pull request. It is categorised as a Write tool in the Bitbucket 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_inline_comment? +

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

What risk level is add_pr_inline_comment? +

add_pr_inline_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_inline_comment? +

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

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

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