delete_messages
Permanently delete only the exact messages in a matching reviewed plan after signed interactive confirmation, durable per-message coordination, one-shot reservation, pending content-free activity, non-retried age-safe execution, and exact 404 readback for every target.
This record as markdown: /tools/app-lasers-guildcontrol-discord/delete-messages.md
What delete_messages does on GuildControl MCP
AI agents call delete_messages 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 delete_messages is rated Critical
Tool irreversibly deletes Discord messages after confirmation; cannot be undone.
From the tool's definition Permanently delete messages; irreversible; exact 404 readback confirmation
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs delete_messages 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 delete_messages, this is the rule to start with:
delete_messages 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 delete_messages call is checked against it from then on.
Questions about delete_messages
Permanently delete only the exact messages in a matching reviewed plan after signed interactive confirmation, durable per-message coordination, one-shot reservation, pending content-free activity, non-retried age-safe execution, and exact 404 readback for every target. 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 delete_messages: 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.
delete_messages 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 delete_messages 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 delete_messages. 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.
delete_messages 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