remove_requested_changes · Bitbucket MCP Server MCP

WHAT IT DOES

What remove_requested_changes does on Bitbucket MCP Server

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

WHY IT NEEDS A POLICY

Why remove_requested_changes needs a policy

This tool removes a previously submitted change request (request for changes review state) from a pull request. This is a reversible modification to the PR review state - the change request can be re-added. It modifies PR metadata but does not delete code, branches, or irreversible data, making it a Write operation.

From the tool's definition Remove change request from a pull request

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_requested_changes Rate-limited

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

FAQ

Questions about remove_requested_changes

What does the remove_requested_changes tool do? +

Remove change request from a pull request. It is categorised as a Write tool in the Bitbucket 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 remove_requested_changes? +

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

What risk level is remove_requested_changes? +

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

Can I rate-limit remove_requested_changes? +

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

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

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