Create a new webhook for a channel. Channel name is fuzzy-matched.
AI agents use create_webhook 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 is a Write operation because it creates a new persistent resource (a webhook) that will remain in the Discord server until explicitly deleted. While not destructive or financial, webhooks can be abused to spam messages, impersonate bots, or integrate malicious external services.
From the tool's definition Tool creates a new webhook for a channel. Webhooks are persistent integrations that enable external systems to post messages to Discord channels.
Documented attack patterns abuse exactly the kind of access create_webhook 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 create_webhook:
{
"version": "1",
"default": "deny",
"tools": {
"create_webhook": {
"limits": [
{
"counter": "create_webhook_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_webhook 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.
Create a new webhook for a channel. Channel name is fuzzy-matched. 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 create_webhook: 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.
create_webhook 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 create_webhook 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 create_webhook. 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.
create_webhook 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.