execute_direct_message_change
Execute one exact reviewed private-message plain-text, static Components V2, or single owned-file send or reply, same-format text or Components V2 edit, or irreversible supported-message deletion only after a fresh matching plan, current exact link-origin enforcement, and signed interactive appro...
This record as markdown: /tools/app-lasers-guildcontrol-discord/execute-direct-message-change.md
What execute_direct_message_change does on GuildControl MCP
AI agents call execute_direct_message_change 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 execute_direct_message_change is rated Critical
Tool permits irreversible message deletion alongside sends/edits; deletion cannot be undone, making it destructive despite safety controls.
From the tool's definition irreversible supported-message deletion, execute one exact reviewed private-message
Attacks that exploit this kind of access
The rule that runs execute_direct_message_change 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 execute_direct_message_change, this is the rule to start with:
execute_direct_message_change 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 execute_direct_message_change call is checked against it from then on.
Questions about execute_direct_message_change
Execute one exact reviewed private-message plain-text, static Components V2, or single owned-file send or reply, same-format text or Components V2 edit, or irreversible supported-message deletion only after a fresh matching plan, current exact link-origin enforcement, and signed interactive approval. Durably coordinates exact user, channel, and message resources; reserves a schema-v2 one-shot request-bound receipt; records content-free pending evidence before contact; applies fixed anti-spam limits and empty mentions; checkpoints newly opened channels and dispatched message IDs; performs no automatic mutation retry; and requires exact presentation, body, receipt-bound attachment metadata, or absence readback. Uncertain outcomes remain quarantined for verify_direct_message_change. 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 execute_direct_message_change: 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.
execute_direct_message_change 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 execute_direct_message_change 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 execute_direct_message_change. 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.
execute_direct_message_change 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