remove_reaction
Remove an emoji reaction from an activity message.
This record as markdown: /tools/dugynoo-huly-mcp/remove-reaction.md
What remove_reaction does on Huly
AI agents call remove_reaction to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_reaction is rated Critical
Removing a reaction is a deletion action (irreversible removal of the reaction association), though the blast radius is minimal since it only affects an emoji reaction on a message. Classified as Destructive due to the removal/delete nature, but severity is low given the negligible impact.
From the tool's definition 'Remove an emoji reaction from an activity message' — removes/deletes a reaction
Attacks that exploit this kind of access
The rule that runs remove_reaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_reaction, this is the rule to start with:
remove_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 Huly, apply this rule, and every remove_reaction call is checked against it from then on.
Questions about remove_reaction
Remove an emoji reaction from an activity message. It is categorised as a Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Huly MCP server in PolicyLayer and add a rule for remove_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 Huly. Nothing to install.
remove_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 remove_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 remove_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.
remove_reaction is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
Across the catalogue