AI agents use slack_react_to_message to create or update resources in Slackxmcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slackxmcp environment.
This tool creates a reversible modification to a message by adding an emoji reaction. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial). The action is easily undoable by removing the reaction, making it a Write operation with low severity since reactions are low-impact metadata changes with minimal blast radius.
From the tool's definition Tool name 'slack_react_to_message' and description 'Add an emoji reaction to a Slack message' indicates a modification operation that adds data (emoji reaction) to an existing message.
Attacks that exploit this kind of access
Add an emoji reaction to a Slack message using the Slack reaction name without surrounding colons. It is categorised as a Write tool in the Slackxmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slackx MCP server in PolicyLayer and add a rule for slack_react_to_message: 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 Slackxmcp. Nothing to install.
slack_react_to_message 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_react_to_message 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_react_to_message. 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_react_to_message is provided by the Slackx MCP server (vaibhavpandeyvpz/slackxmcp). 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 →