reopen_pull_request_comment · Bitbucket Server MCP

WHAT IT DOES

What reopen_pull_request_comment does on Bitbucket Server MCP

AI agents use reopen_pull_request_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 reopen_pull_request_comment needs a policy

Reopening a pull request comment is a write operation that modifies existing data (comment state) reversibly. It does not delete data, execute arbitrary code, or create financial obligations. The context of sibling tools (create_pull_request_comment, approve_pull_request) confirms this is part of the PR management suite where state transitions are Write-category operations.

From the tool's definition Tool name 'reopen_pull_request_comment' indicates modifying the state of a pull request comment by reopening it, which is a reversible state change operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reopen_pull_request_comment Rate-limited

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

FAQ

Questions about reopen_pull_request_comment

What does the reopen_pull_request_comment tool do? +

reopen_pull_request_comment. 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 reopen_pull_request_comment? +

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

What risk level is reopen_pull_request_comment? +

reopen_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 reopen_pull_request_comment? +

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

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

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