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.
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.
Documented attack patterns abuse exactly the kind of access slack_reactions_add gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for slack_reactions_add:
{
"version": "1",
"default": "deny",
"tools": {
"slack_reactions_add": {
"limits": [
{
"counter": "slack_reactions_add_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
slack_reactions_add 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_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.
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.
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.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.