plan_webhook_message_deletion
Prepare a process-bound keyed plan to permanently delete one exact message authored by one privately managed Incoming webhook. Verifies credential-to-webhook identity, direct scoped channel identity, exact transient message content and metadata, the privacy boundary, a transient local review reas...
This record as markdown: /tools/app-lasers-guildcontrol-discord/plan-webhook-message-deletion.md
What plan_webhook_message_deletion does on GuildControl MCP
AI agents call plan_webhook_message_deletion to permanently remove resources in GuildControl MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why plan_webhook_message_deletion is rated Critical
Tool irreversibly deletes Discord messages with permanent effect, though scoped to single messages and requiring credential verification.
From the tool's definition permanently delete one exact message authored by one privately managed Incoming webhook
Attacks that exploit this kind of access
The rule that runs plan_webhook_message_deletion 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 plan_webhook_message_deletion, this is the rule to start with:
plan_webhook_message_deletion is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect GuildControl MCP, apply this rule, and every plan_webhook_message_deletion call is checked against it from then on.
Questions about plan_webhook_message_deletion
Prepare a process-bound keyed plan to permanently delete one exact message authored by one privately managed Incoming webhook. Verifies credential-to-webhook identity, direct scoped channel identity, exact transient message content and metadata, the privacy boundary, a transient local review reason, and a unique one-shot operation key without writing or persisting message content. It is categorised as a Destructive tool in the GuildControl MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GuildControl MCP server in PolicyLayer and add a rule for plan_webhook_message_deletion: 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.
plan_webhook_message_deletion is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the plan_webhook_message_deletion 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 plan_webhook_message_deletion. 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.
plan_webhook_message_deletion 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.
Across the catalogue