AI agents use send_webhook_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.
This tool creates/posts new data (messages) to Discord, which is reversible (messages can be deleted). It does not execute code, delete data irreversibly, or move money. The 'medium' severity reflects that an AI agent could spam messages, impersonate users via custom usernames/avatars, or post harmful content to Discord servers, but the effects are not irreversible and limited to message creation.
From the tool's definition Tool name 'send_webhook_message' and description state it sends messages through Discord webhooks with custom username/avatar customization. This creates new message data in Discord.
Attacks that exploit this kind of access
Send a message through a Discord webhook. Supports custom username and avatar. 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_webhook_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_webhook_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_webhook_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_webhook_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_webhook_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 →