Send a direct message to a server member. The member is resolved by name, ID, or mention using fuzzy matching.
AI agents use send_dm 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.
This tool creates and sends a new message to a Discord user, which is a reversible write operation. While it doesn't modify or delete existing data, it does create new communication records. Severity is medium because unsolicited or inappropriate messages could constitute harassment or social engineering, but the action is not destructive, financial, or system-level code execution.
From the tool's definition The tool 'send_dm' performs message creation and delivery ('Send a direct message'), which is a write operation that creates new data (the message) in Discord's system.
Documented attack patterns abuse exactly the kind of access send_dm 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 send_dm:
{
"version": "1",
"default": "deny",
"tools": {
"send_dm": {
"limits": [
{
"counter": "send_dm_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} send_dm stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Send a direct message to a server member. The member is resolved by name, ID, or mention using fuzzy matching. 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_dm: 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_dm 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_dm 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_dm. 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_dm 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.