Get all reactions on a message, including every user who reacted and their detailed member info (account creation date, server join date, roles, etc.). Channel name is fuzzy-matched.
AI agents call get_reactions to retrieve information from Discord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is fundamentally a data retrieval operation—it queries and returns existing reactions and user information without creating, modifying, or deleting anything. However, severity is elevated to 'medium' rather than 'low' because it exposes detailed personal/account information (creation dates, join dates, role assignments) about Discord users, which could enable privacy violations, user profiling, or…
From the tool's definition Tool description explicitly states 'Get all reactions on a message' with no modification or side effects. Returns user identity and metadata (account creation date, join date, roles).
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access get_reactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Discord, and nothing reaches the server without passing your rules. This is the rule we recommend for get_reactions:
{
"version": "1",
"default": "deny",
"tools": {
"get_reactions": {}
}
}get_reactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all reactions on a message, including every user who reacted and their detailed member info (account creation date, server join date, roles, etc.). Channel name is fuzzy-matched. It is categorised as a Read tool in the Discord MCP Server, which means it retrieves data without modifying state.
Register the Discord MCP server in PolicyLayer and add a rule for get_reactions: 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. Nothing to install.
get_reactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_reactions 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 get_reactions. 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.
get_reactions is provided by the Discord MCP server (hardheadhackerhead/discord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Discord, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
139 Discord tools catalogued and risk-classified — across an index of 43,000+ MCP servers.