Add a reaction emoji to a message
AI agents use slack_add_reaction to create or update resources in Slack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack MCP Server environment.
Adding a reaction is a write operation that modifies message metadata (adds an emoji reaction) but is fully reversible (reactions can be removed). It has minimal blast radius—worst case an agent adds many reactions causing minor spam or confusion. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete anything (Destructive), or move money (Financial).
From the tool's definition Tool description states 'Add a reaction emoji to a message' — this creates/modifies a reaction object on an existing message, a reversible change to message state.
Attacks that exploit this kind of access
Add a reaction emoji to a message. It is categorised as a Write tool in the Slack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slack MCP Server MCP server in PolicyLayer and add a rule for slack_add_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 Slack MCP Server. Nothing to install.
slack_add_reaction is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the slack_add_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 slack_add_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.
slack_add_reaction is provided by the Slack MCP Server MCP server (lbeatu/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 →