send_webhook_message
Send one bounded plain-text message through one privately managed Discord Incoming webhook with exact allowlisted user notifications, empty role and everyone mention parsing, suppressed embeds, per-channel anti-spam limits, a durable one-shot operation key, one non-retried mutation, and exact res...
This record as markdown: /tools/app-lasers-guildcontrol-discord/send-webhook-message.md
What send_webhook_message does on GuildControl MCP
AI agents use send_webhook_message to create or update resources in GuildControl MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GuildControl MCP environment.
Why send_webhook_message is rated Medium
Tool creates messages in Discord reversibly; bounded, audited, with anti-spam controls and no persistence mitigates severity.
From the tool's definition Send message through webhook; one-shot operation; mutations; notification parsing
Attacks that exploit this kind of access
The rule that runs send_webhook_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GuildControl MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_webhook_message, this is the rule to start with:
send_webhook_message 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 GuildControl MCP, apply this rule, and every send_webhook_message call is checked against it from then on.
Questions about send_webhook_message
Send one bounded plain-text message through one privately managed Discord Incoming webhook with exact allowlisted user notifications, empty role and everyone mention parsing, suppressed embeds, per-channel anti-spam limits, a durable one-shot operation key, one non-retried mutation, and exact response plus readback verification. The credential and execution URL never enter MCP data or durable records; message content is not persisted. It is categorised as a Write tool in the GuildControl MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GuildControl 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 GuildControl MCP. 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 GuildControl MCP server (guildctl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GuildControl, and thousands of servers like it.
This server
Across the catalogue