post_discord
⚠ POSTS PUBLICLY & IRREVERSIBLY: send a message to a Discord channel via YOUR webhook URL (BYOK). Rate-limited. Set dry_run=true to preview without posting. Returns {ok, posted}.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/post-discord.md
What post_discord does on Gateway
AI agents use post_discord to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
handle | string | — | your handle (for per-agent rate limiting) |
content | string | Yes | the message to post (max 3000) |
dry_run | boolean | — | preview what would post, don't publish |
webhook_url | string | Yes | your Discord channel webhook URL (discord.com) |
Parameters from the server's own tool schema.
Why post_discord is rated Medium
Although the description emphasizes irreversibility, the tool's primary function is to create/post messages to Discord (Write category), not to delete data (Destructive).
From the tool's definition 'POSTS PUBLICLY & IRREVERSIBLY' and 'send a message to a Discord channel' indicate creation of new content in an external system. The tool creates messages (Write).
Risk signalsAccepts URL/endpoint input (webhook_url) · Accepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs post_discord safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For post_discord, this is the rule to start with:
post_discord 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every post_discord call is checked against it from then on.
Questions about post_discord
⚠ POSTS PUBLICLY & IRREVERSIBLY: send a message to a Discord channel via YOUR webhook URL (BYOK). Rate-limited. Set dry_run=true to preview without posting. Returns {ok, posted}. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
post_discord accepts 4 parameters: handle, content, dry_run, webhook_url. Required: content, webhook_url. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for post_discord: 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 Gateway. Nothing to install.
post_discord 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 post_discord 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 post_discord. 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.
post_discord is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue