reactions_remove

A destructive tool on the Slack MCP server.

SERVERSlack SOURCEkarbassi/slack-mcp

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/karbassi-slack-mcp/reactions-remove.md

WHAT IT DOES

What reactions_remove does on Slack

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.

RISK

Why reactions_remove is rated Critical

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

RECOMMENDED RULE

The rule that runs reactions_remove safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reactions_remove, this is the rule to start with:

reactions_remove Hidden

reactions_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "reactions_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every reactions_remove call is checked against it from then on.

FAQ

Questions about reactions_remove

What does the reactions_remove tool do? +

reactions_remove is a destructive tool on the Slack MCP server. 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.

How do I enforce a policy on reactions_remove? +

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.

What risk level is reactions_remove? +

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

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.

How do I block reactions_remove completely? +

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.

What MCP server provides reactions_remove? +

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.

KEEP EXPLORING

More on Slack, and thousands of servers like it.

This server

All 233 Slack tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →