slack_reactions_remove

Remove an emoji reaction from a message

SERVERSage MCP SOURCEsagemcp/sagemcp

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

WHAT IT DOES

What slack_reactions_remove does on Sage MCP

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

RISK

Why slack_reactions_remove is rated Critical

Removing a reaction is a deletion operation that cannot be trivially undone (the original reaction state is lost). While the blast radius is limited — only an emoji reaction is deleted, not a message or channel — it is still an irreversible removal of existing data, placing it in the Destructive category at medium severity.

From the tool's definition 'Remove an emoji reaction from a message' — the word 'remove' indicates deletion of existing data (the reaction)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs slack_reactions_remove safely

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

slack_reactions_remove Hidden

slack_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": [
    "slack_reactions_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about slack_reactions_remove

What does the slack_reactions_remove tool do? +

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

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

What risk level is slack_reactions_remove? +

slack_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 slack_reactions_remove? +

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

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

slack_reactions_remove is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage 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 →