comment_id

Reference a comment by ID for operations

Can modify PR discussion comments

Part of the Bitbucket MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents use comment_id to create or modify resources in Bitbucket MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON COMMENT_ID

Without a policy, an AI agent could call comment_id repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Bitbucket MCP.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

bitbucket-mcp.yaml

tools:
  comment_id:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Bitbucket MCP policy for all 16 tools.

// DETAILS

Tool Name comment_id

Category Write

MCP Server Bitbucket MCP MCP Server

Risk Level Medium

// MORE BITBUCKET MCP TOOLS

Execute target Read all Read content Read description Read limit Read page Read pagelen Read pull_request_id

View all 16 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like comment_id have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the comment_id tool do? +

Reference a comment by ID for operations. It is categorised as a Write tool in the Bitbucket 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 comment_id? +

Add a rule in your Intercept YAML policy under the tools section for comment_id. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Bitbucket MCP MCP server.

What risk level is comment_id? +

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

Can I rate-limit comment_id? +

Yes. Add a rate_limit block to the comment_id rule in your Intercept 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 comment_id completely? +

Set action: deny in the Intercept policy for comment_id. 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 comment_id? +

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

comment_id

Enforce policies on Bitbucket MCP