Add a reaction emoji to a message
AI agents use slack_add_reaction to create or update resources in Simple Slack — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Simple Slack environment.
This tool creates new data (a reaction) in Slack, making it a Write operation rather than Read. While reversible (reactions can be removed), it modifies server state. Severity is medium because reactions are low-impact communications—unlikely to cause significant harm even if misused by an AI agent, though it could enable spam or harassment if chained with message enumeration.
From the tool's definition The tool description states it will 'Add a reaction emoji to a message', which creates a new reaction object/state in Slack. This is a modification operation that changes the message's metadata reversibly.
Attacks that exploit this kind of access
Add a reaction emoji to a message. It is categorised as a Write tool in the Simple Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Simple Slack 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 Simple Slack. 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 Simple Slack MCP server (bugzy-ai/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 →