AI agents call deletePullRequestComment to permanently remove resources in Bitbucket MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a pull request comment, which cannot be undone. Deletion is an irreversible action that destroys data. While the blast radius is somewhat limited to a single comment rather than an entire repository, the inability to recover the deleted comment and its potential discussion context makes this a destructive operation.
From the tool's definition The tool is named 'deletePullRequestComment' with description 'Delete a comment on a pull request'. The verb 'Delete' and the irreversible nature of removing a comment from a pull request explicitly fall under the Destructive category.
Documented attack patterns abuse exactly the kind of access deletePullRequestComment gives an agent:
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 deletePullRequestComment:
{
"version": "1",
"default": "deny",
"hide": [
"deletePullRequestComment"
]
}deletePullRequestComment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a comment on 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.
Register the Bitbucket MCP server in PolicyLayer and add a rule for deletePullRequestComment: 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.
deletePullRequestComment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deletePullRequestComment 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.
Set action: deny in the PolicyLayer policy for deletePullRequestComment. 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.
deletePullRequestComment 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.
Start from Bitbucket MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
49 Bitbucket MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.