New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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...

SERVERGuildControl MCP SOURCEguildctl
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about send_webhook_message

What does the send_webhook_message tool do? +

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.

How do I enforce a policy on send_webhook_message? +

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.

What risk level is send_webhook_message? +

send_webhook_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit send_webhook_message? +

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.

How do I block send_webhook_message completely? +

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.

What MCP server provides send_webhook_message? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GuildControl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.