AI agents use slack_add_reaction to create or update resources in Slack — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack environment.
Adding a reaction is a Write operation because it creates/modifies data (the emoji reaction on a message) in a reversible manner. Users can remove reactions, making this non-destructive. Severity is low because the blast radius of misuse is minimal—unwanted emoji reactions have no financial impact, do not compromise sensitive data access, and can be easily undone. This is a safe social metadata operation.
From the tool's definition Tool description explicitly states 'Add a reaction emoji to a message', which is a reversible modification to message metadata. The tool creates/modifies state (adds an emoji reaction) without deleting or executing external code.
Documented attack patterns abuse exactly the kind of access slack_add_reaction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Slack, and nothing reaches the server without passing your rules. This is the rule we recommend for slack_add_reaction:
{
"version": "1",
"default": "deny",
"tools": {
"slack_add_reaction": {
"limits": [
{
"counter": "slack_add_reaction_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}slack_add_reaction 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.
Free to start. No card required.
Add a reaction emoji to a message. It is categorised as a Write tool in the Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 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 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 Slack MCP server (zencoderai/slack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Slack tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Slack tools catalogued and risk-classified — across an index of 42,500+ MCP servers.