slack_reactions_add

Add an emoji reaction to a message

SERVERSage MCP SOURCEsagemcp/sagemcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/slack-reactions-add.md

WHAT IT DOES

What slack_reactions_add does on Sage MCP

AI agents use slack_reactions_add to create or update resources in Sage MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sage MCP environment.

RISK

Why slack_reactions_add is rated Medium

Adding an emoji reaction to a message creates new data (the reaction) but is easily reversible (can be removed), does not delete or overwrite existing content irreversibly, does not execute code or trigger external operations, and has minimal blast radius if misused by an AI agent. This is a straightforward Write operation with low severity.

From the tool's definition Tool name 'slack_reactions_add' and description 'Add an emoji reaction to a message' indicate creation of a reaction entity on an existing message, which is a reversible modification of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs slack_reactions_add 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_add, this is the rule to start with:

slack_reactions_add Rate-limited

slack_reactions_add stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "slack_reactions_add": {
      "limits": [
        {
          "counter": "slack_reactions_add_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_add call is checked against it from then on.

FAQ

Questions about slack_reactions_add

What does the slack_reactions_add tool do? +

Add an emoji reaction to a message. It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on slack_reactions_add? +

Register the Sage MCP server in PolicyLayer and add a rule for slack_reactions_add: 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_add? +

slack_reactions_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit slack_reactions_add? +

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

Set action: deny in the PolicyLayer policy for slack_reactions_add. 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_add? +

slack_reactions_add 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 →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →