remove_pr_comment_reaction

Remove an emoticon reaction from a pull request comment. Only the user who added the reaction can remove it. Supported emoticons: thumbsup, thumbsdown, heart, thinking_face, laughing.

Server Mcp Bitbucket Server mcp-bitbucket-server
Category Destructive
Risk class Critical
Parameters 00 required

What remove_pr_comment_reaction does on Mcp Bitbucket Server

AI agents call remove_pr_comment_reaction 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.

Why remove_pr_comment_reaction needs a policy

The tool irreversibly removes a reaction from a PR comment. While the blast radius is very low (only an emoji reaction is deleted, not content), the action is a deletion that cannot be undone, placing it in the Destructive category. Severity is low because the impact is minimal — only a cosmetic emoji reaction is affected.

From the tool's definition Remove an emoticon reaction from a pull request comment. Only the user who added the reaction can remove it.

Questions about remove_pr_comment_reaction

What does the remove_pr_comment_reaction tool do? +

Remove an emoticon reaction from a pull request comment. Only the user who added the reaction can remove it. Supported emoticons: thumbsup, thumbsdown, heart, thinking_face, laughing. 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.

How do I enforce a policy on remove_pr_comment_reaction? +

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

remove_pr_comment_reaction 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 remove_pr_comment_reaction? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.