deletePullRequestTask

THE RISK

Critical Risk

Why deletePullRequestTask needs a policy

Deletion of pull request tasks is an irreversible action that destroys data without recovery possibility. While the blast radius is somewhat limited to project collaboration metadata (not production code or financial systems), the permanent removal of PR task records could disrupt project workflows, lose important tracking information, or remove accountability records.

From the tool's definition Tool name 'deletePullRequestTask' and description 'Delete a task from a pull request' explicitly perform deletion, which is irreversible data removal.

Documented attack patterns abuse exactly the kind of access deletePullRequestTask gives an agent:

POLICY

How to control deletePullRequestTask

PolicyLayer is an MCP gateway — it sits between your AI agents and Bitbucket MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for deletePullRequestTask:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "deletePullRequestTask"
  ]
}

deletePullRequestTask disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Bitbucket MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bitbucket MCP tools

Destructive deletePullRequestComment Delete a comment on a pull request Execute runPipeline Trigger a new pipeline run Execute stopPipeline Stop a running pipeline Write unapprovePullRequest Remove approval from a pull request Write declinePullRequest Decline a pull request Write addPendingPullRequestComment Add a pending (draft) comment to a pull request that can be published later Write addPullRequestComment Add a comment to a pull request (general, inline, or a threaded reply to another comment) Write approvePullRequest Approve a pull request

All 49 Bitbucket MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Bitbucket MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about deletePullRequestTask

What does the deletePullRequestTask tool do? +

Delete a task from a pull request. It is categorised as a Destructive tool in the Bitbucket MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on deletePullRequestTask? +

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

What risk level is deletePullRequestTask? +

deletePullRequestTask is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deletePullRequestTask? +

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

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

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

Enforce policy on every Bitbucket MCP tool call.

Start from Bitbucket MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →