Delete a pull request comment. You can delete your own comments. Only REPO_ADMIN users can delete comments created by others. Comments with replies cannot be deleted. You must provide the comment version to prevent concurrent modification conflicts - get the version from the comment object.
AI agents call delete_pr_comment to permanently remove resources in Mcp Bitbucket Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes pull request comments, which cannot be undone. Deletion is a destructive operation that removes data from the system. While the impact is scoped to individual comments rather than entire repositories, an AI agent with misused permissions could maliciously delete important discussion context or hide critical review feedback during the pull request process.
From the tool's definition delete_pr_comment: 'Delete a pull request comment' - the tool permanently removes data (comments) from a pull request, with the note that 'Comments with replies cannot be deleted' indicating irreversible deletion of modifiable content.
Attacks that exploit this kind of access
Delete a pull request comment. You can delete your own comments. Only REPO_ADMIN users can delete comments created by others. Comments with replies cannot be deleted. You must provide the comment version to prevent concurrent modification conflicts - get the version from the comment object. It is categorised as a Destructive tool in the Mcp Bitbucket Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Bitbucket Server MCP server in PolicyLayer and add a rule for delete_pr_comment: 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.
delete_pr_comment 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 delete_pr_comment 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 delete_pr_comment. 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.
delete_pr_comment 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →