add_inline_comment · Bitbucket Server MCP: Risk & Policy

WHAT IT DOES

What add_inline_comment does on Bitbucket Server MCP

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

WHY IT NEEDS A POLICY

Why add_inline_comment needs a policy

This tool creates new data (a comment) in a pull request, which is a Write-category operation. It is reversible (comments can be deleted or edited) and has no destructive or financial impact. Severity is medium because uncontrolled commenting could spam pull requests or add misleading code review feedback, but the blast radius is limited to the specific pull request and can be remediated.

From the tool's definition The tool 'add_inline_comment' creates a new comment on a file within a pull request, as stated in its description: 'Add an inline comment to a file in a pull request'. This is a write operation that modifies the pull request by adding reversible content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_inline_comment Rate-limited

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

FAQ

Questions about add_inline_comment

What does the add_inline_comment tool do? +

Add an inline comment to a file in a pull request. It is categorised as a Write tool in the Bitbucket Server MCP 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_inline_comment? +

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

What risk level is add_inline_comment? +

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

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

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

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