execute_bulk_guild_ban
Execute one exact reviewed native Discord bulk guild ban after host write approval, signed interactive approval, a final fresh evidence match, durable coordination across every exact member target, one-shot receipt reservation, and pending content-free activity. Dispatches once without retry, rep...
This record as markdown: /tools/app-lasers-guildcontrol-discord/execute-bulk-guild-ban.md
What execute_bulk_guild_ban does on GuildControl MCP
AI agents call execute_bulk_guild_ban 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_bulk_guild_ban is rated Critical
Banning multiple guild members is irreversible and affects many users simultaneously.
From the tool's definition bulk guild ban... dispatches once without retry... every exact member target
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs execute_bulk_guild_ban 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_bulk_guild_ban, this is the rule to start with:
execute_bulk_guild_ban 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_bulk_guild_ban call is checked against it from then on.
Questions about execute_bulk_guild_ban
Execute one exact reviewed native Discord bulk guild ban after host write approval, signed interactive approval, a final fresh evidence match, durable coordination across every exact member target, one-shot receipt reservation, and pending content-free activity. Dispatches once without retry, reports partial success explicitly, and requires fresh exact 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 execute_bulk_guild_ban: 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_bulk_guild_ban 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_bulk_guild_ban 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_bulk_guild_ban. 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_bulk_guild_ban 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