update_review_status · Mcp Bitbucket Server MCP

WHAT IT DOES

What update_review_status does on Mcp Bitbucket Server

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

WHY IT NEEDS A POLICY

Why update_review_status needs a policy

This tool modifies pull request metadata (review status) by the authenticated user. The change is reversible—review status can be updated again. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or have the irreversibility of destructive operations. Classification as Write is appropriate.

From the tool's definition Tool name 'update_review_status' and description 'Change the review status for a pull request' indicate modification of pull request review state, a reversible data change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_review_status Rate-limited

update_review_status 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": {
    "update_review_status": {
      "limits": [
        {
          "counter": "update_review_status_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 Mcp Bitbucket Server, so you can run agents against it safely.

FAQ

Questions about update_review_status

What does the update_review_status tool do? +

Change the review status for a pull request. Sets the authenticated user\. It is categorised as a Write tool in the Mcp Bitbucket 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 update_review_status? +

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

What risk level is update_review_status? +

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

Can I rate-limit update_review_status? +

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

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

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