add_slack_reaction
AI agents use add_slack_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 reactions to Slack messages is a Write operation—it creates new metadata/state on existing messages. While reversible (reactions can be removed), it modifies shared workspace data that other users see. Severity is medium because the blast radius of unwanted reaction spam is limited to aesthetic/UX disruption without affecting critical data or financial systems.
From the tool's definition Tool name 'add_slack_reaction' indicates adding/creating a reaction emoji to a message, modifying message state in Slack. Description is empty, limiting evidence.
Attacks that exploit this kind of access
add_slack_reaction. 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 add_slack_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.
add_slack_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 add_slack_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 add_slack_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.
add_slack_reaction is provided by the Slack MCP Server MCP server (yeoamlog/slack-mcp-server). 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 →