update_pull_request_task · Bitbucket Server MCP

WHAT IT DOES

What update_pull_request_task does on Bitbucket Server MCP

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

This is classified as Write rather than Read because 'update' is a mutating operation that modifies data reversibly. It is not Destructive (no deletion), Execute (no code/command execution), Financial (no money movement), or other categories.

From the tool's definition Tool name is 'update_pull_request_task' with no description provided. The 'update' verb indicates modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_pull_request_task Rate-limited

update_pull_request_task 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_pull_request_task": {
      "limits": [
        {
          "counter": "update_pull_request_task_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 update_pull_request_task

What does the update_pull_request_task tool do? +

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

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

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

Can I rate-limit update_pull_request_task? +

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

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

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