bb_request_changes_pull_request

WHAT IT DOES

What bb_request_changes_pull_request does on Bitbucket Cloud MCP Server

AI agents use bb_request_changes_pull_request 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_request_changes_pull_request needs a policy

Requesting changes on a pull request is a reversible write operation that modifies the PR's review status. It does not delete data, execute code, or involve financial transactions. The action can be undone by approving or removing the change request. Severity is medium because misuse could block legitimate PRs from merging.

From the tool's definition "Request changes on a pull request" — this modifies the review state of a pull request by adding a change-request review

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bb_request_changes_pull_request Rate-limited

bb_request_changes_pull_request 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_request_changes_pull_request": {
      "limits": [
        {
          "counter": "bb_request_changes_pull_request_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_request_changes_pull_request

What does the bb_request_changes_pull_request tool do? +

Request changes 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_request_changes_pull_request? +

Register the Bitbucket Cloud MCP Server MCP server in PolicyLayer and add a rule for bb_request_changes_pull_request: 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_request_changes_pull_request? +

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

Can I rate-limit bb_request_changes_pull_request? +

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

Set action: deny in the PolicyLayer policy for bb_request_changes_pull_request. 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_request_changes_pull_request? +

bb_request_changes_pull_request 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.