Adds an emoji reaction to a specific Discord message
AI agents use discord_add_reaction to create or update resources in MCP-Discord — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Discord environment.
Adding reactions modifies message state by creating new reaction metadata, which qualifies as a Write operation. The severity is low because reactions are ephemeral, reversible metadata with minimal blast radius—a user can easily remove unwanted reactions. This does not permanently alter message content, delete data, execute code, or incur financial consequences.
From the tool's definition Tool adds an emoji reaction to a Discord message. This is a create operation (adding a reaction where none existed) that is reversible (reactions can be removed).
Attacks that exploit this kind of access
Adds an emoji reaction to a specific Discord message. It is categorised as a Write tool in the MCP-Discord MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-Discord MCP server in PolicyLayer and add a rule for discord_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 MCP-Discord. Nothing to install.
discord_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 discord_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 discord_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.
discord_add_reaction is provided by the MCP-Discord MCP server (jackedelic/mcp-discord). 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 →