reactions_remove
AI agents call reactions_remove to permanently remove resources in Slack — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a reaction is an irreversible deletion action (reactions cannot be 'unremoved' without re-adding them). The name follows the pattern of destructive operations. Confidence is reduced due to empty description, but the naming convention in Slack APIs is consistent — reactions.remove deletes an emoji reaction from a message.
From the tool's definition Tool name 'reactions_remove' strongly implies removal/deletion of a reaction. Description is empty, so classification is based on name alone.
Attacks that exploit this kind of access
reactions_remove. It is categorised as a Destructive tool in the Slack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Slack MCP server in PolicyLayer and add a rule for reactions_remove: 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 Slack. Nothing to install.
reactions_remove 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 reactions_remove 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 reactions_remove. 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.
reactions_remove is provided by the Slack MCP server (karbassi/slack-mcp). 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 →