delete_work_item_note_emoji_reaction
Remove an emoji reaction from a work item note (comment, thread, or thread reply)
This record as markdown: /tools/io-github-zereight-gitlab-mcp/delete-work-item-note-emoji-reaction.md
What delete_work_item_note_emoji_reaction does on Gitlab Mcp
AI agents call delete_work_item_note_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_work_item_note_emoji_reaction is rated Critical
This tool permanently removes data (an emoji reaction) from a work item note. While the scope is narrow (a single emoji reaction rather than entire objects), it is destructive in nature—the deletion is irreversible and represents loss of user-contributed content. An AI agent misusing this could maliciously strip reactions from discussions, altering the historical record of team feedback or sentiment.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Remove an emoji reaction from a work item note'. The action irreversibly deletes user-created metadata (emoji reactions) that cannot be automatically undone.
Attacks that exploit this kind of access
The rule that runs delete_work_item_note_emoji_reaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_work_item_note_emoji_reaction, this is the rule to start with:
delete_work_item_note_emoji_reaction is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every delete_work_item_note_emoji_reaction call is checked against it from then on.
Questions about delete_work_item_note_emoji_reaction
Remove an emoji reaction from a work item note (comment, thread, or thread reply). 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.
Register the Gitlab MCP server in PolicyLayer and add a rule for delete_work_item_note_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.
delete_work_item_note_emoji_reaction 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_work_item_note_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.
Set action: deny in the PolicyLayer policy for delete_work_item_note_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.
delete_work_item_note_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.
Across the catalogue