delete_issue_emoji_reaction

Remove an emoji reaction from an issue

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/delete-issue-emoji-reaction.md

What delete_issue_emoji_reaction does on Gitlab Mcp

AI agents call delete_issue_emoji_reaction to permanently remove resources in Gitlab Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_issue_emoji_reaction is rated Critical

The tool irreversibly removes an emoji reaction from an issue, which cannot be undone through normal use. While the blast radius is low (only affects a single emoji reaction with minimal consequences), it is destructive in nature because the deletion is permanent. This maps to the Destructive category per the rules: actions that cannot be undone. Severity is low because the impact scope is narrow and inconsequential.

From the tool's definition Tool name contains 'delete' and description states 'Remove an emoji reaction from an issue', indicating irreversible removal of data.

Questions about delete_issue_emoji_reaction

What does the delete_issue_emoji_reaction tool do? +

Remove an emoji reaction from an issue. It is categorised as a Destructive tool in the Gitlab 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 delete_issue_emoji_reaction? +

Register the Gitlab MCP server in PolicyLayer and add a rule for delete_issue_emoji_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 Gitlab Mcp. Nothing to install.

What risk level is delete_issue_emoji_reaction? +

delete_issue_emoji_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 delete_issue_emoji_reaction? +

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

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

delete_issue_emoji_reaction is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Gitlab, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gitlab's. Pull the full record:

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.