bb_unresolve_pull_request_comment

WHAT IT DOES

What bb_unresolve_pull_request_comment does on Bitbucket Cloud MCP Server

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

WHY IT NEEDS A POLICY

Why bb_unresolve_pull_request_comment needs a policy

This tool modifies comment metadata/state but does not delete data or create permanent records. While it changes the visibility or status of a comment thread, the action is reversible (can be resolved again). It affects collaboration/review workflow but has limited blast radius. Classified as Write rather than Execute because it updates a specific data field rather than executing arbitrary logic.

From the tool's definition Tool description states it will 'reopen a resolved comment thread' on a pull request, which modifies the state of a comment (from resolved to unresolved). This is a reversible state change to existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bb_unresolve_pull_request_comment Rate-limited

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

FAQ

Questions about bb_unresolve_pull_request_comment

What does the bb_unresolve_pull_request_comment tool do? +

Reopen a resolved comment thread on a pull request. It is categorised as a Write tool in the Bitbucket Cloud MCP 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 bb_unresolve_pull_request_comment? +

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

What risk level is bb_unresolve_pull_request_comment? +

bb_unresolve_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 bb_unresolve_pull_request_comment? +

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

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

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