execute_role_deletion
Permanently delete one exact reviewed standard Discord role only after a fresh matching keyed plan, the identical recovery choice, and signed interactive approval of the credential-free recovery evidence and limitations. Signed request state binds only the attestation hash, never the raw attestat...
This record as markdown: /tools/app-lasers-guildcontrol-discord/execute-role-deletion.md
What execute_role_deletion does on GuildControl MCP
AI agents call execute_role_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 execute_role_deletion is rated Critical
Irreversibly deletes Discord roles; cannot be undone despite mitigations like approval and recovery planning.
From the tool's definition Permanently delete one exact reviewed standard Discord role only after fresh matching keyed plan
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs execute_role_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 execute_role_deletion, this is the rule to start with:
execute_role_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 execute_role_deletion call is checked against it from then on.
Questions about execute_role_deletion
Permanently delete one exact reviewed standard Discord role only after a fresh matching keyed plan, the identical recovery choice, and signed interactive approval of the credential-free recovery evidence and limitations. Signed request state binds only the attestation hash, never the raw attestation. Durably coordinates the target and every reviewed guild collection, reserves a one-shot key, records pending content-free evidence, sends one non-retried DELETE, and requires fresh target-absence and survivor-preservation evidence. Never persists an attestation, treats an absent target as success, cleans up references, retries, or rolls back. 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_role_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.
execute_role_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 execute_role_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 execute_role_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.
execute_role_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