Send a direct message to a Discord user. Args: user_id: Target user's Discord ID. content: Message content.
AI agents use discord_create_dm to create or update resources in autoMate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your autoMate environment.
This tool creates new data (a message) in an external service (Discord) and is reversible (messages can be deleted). It does not execute arbitrary code, delete data, or move money.
From the tool's definition Tool creates a new message by sending a direct message to a Discord user via arguments user_id and content. The description explicitly states 'Send a direct message', which is a write operation that creates data (a message record) in Discord.
Documented attack patterns abuse exactly the kind of access discord_create_dm gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for discord_create_dm:
{
"version": "1",
"default": "deny",
"tools": {
"discord_create_dm": {
"limits": [
{
"counter": "discord_create_dm_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}discord_create_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 Discord user. Args: user_id: Target user's Discord ID. content: Message content. It is categorised as a Write tool in the autoMate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the autoMate MCP server in PolicyLayer and add a rule for discord_create_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 autoMate. Nothing to install.
discord_create_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 discord_create_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 discord_create_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.
discord_create_dm is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.