AI agents use send_message to create or update resources in Discord — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Discord environment.
Sending a message is a write operation that creates new data. While it has no direct financial impact and is reversible (unlike destructive actions), an AI agent with unconstrained access could spam channels, impersonate users, leak sensitive information, or harass users at scale. Medium severity reflects the moderate blast radius and reputational/disruption harm, though not data loss or financial consequence.
From the tool's definition Tool description states 'Send a message to a Discord channel' which creates new data (a message) that is reversible (messages can be edited or deleted). The action modifies server state by adding content.
Attacks that exploit this kind of access
Send a message to a Discord channel. Supports plain text. Returns the sent message ID. It is categorised as a Write tool in the Discord MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Discord MCP server in PolicyLayer and add a rule for send_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. Nothing to install.
send_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 send_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 send_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.
send_message is provided by the Discord MCP server (ngoctranfire/discord-mcp-server). 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 →