Send a message with a file attachment to a channel. The file can be specified by URL.
AI agents use send_message_with_file 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 new data (a Discord message with file attachment) in a channel, which is a Write operation. It is not Read (no data retrieval), not Execute (does not run code or trigger arbitrary operations), not Destructive (messages are deletable), and not Financial.
From the tool's definition Tool name 'send_message_with_file' and description 'Send a message with a file attachment to a channel' indicate creation of new content (a message with attachment) that is reversible (messages can be deleted).
Documented attack patterns abuse exactly the kind of access send_message_with_file 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_message_with_file:
{
"version": "1",
"default": "deny",
"tools": {
"send_message_with_file": {
"limits": [
{
"counter": "send_message_with_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} send_message_with_file 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 message with a file attachment to a channel. The file can be specified by URL. 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_with_file: 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_with_file 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_with_file 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_with_file. 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_with_file 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.