Add a reaction emoji to a message
AI agents use react-to-message to create or update resources in Discord MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Discord MCP Server environment.
Reactions are user-facing message metadata that can be added and removed. This is a reversible modification operation, placing it squarely in the Write category. The blast radius is minimal — an unwanted emoji reaction is trivial to undo and causes no harm. Severity is low.
From the tool's definition Tool performs 'add a reaction emoji to a message' — this creates/modifies a message's associated data (reactions) reversibly. Adding a reaction is not destructive, does not execute arbitrary code, and does not involve financial operations.
Attacks that exploit this kind of access
Add a reaction emoji to a message. It is categorised as a Write tool in the Discord MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Discord MCP Server MCP server in PolicyLayer and add a rule for 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 Discord MCP Server. Nothing to install.
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 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 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.
react-to-message is provided by the Discord MCP Server MCP server (rossh121/discord-mcp). 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 →