plan_guild_prune
Prepare a process-bound keyed plan for one bounded non-exact Discord guild prune. Verifies pinned identity, exact guild and include-role policy, complete KICK_MEMBERS plus MANAGE_GUILD evidence, safe role widening, protected-identity shields, a fresh native count estimate, two pre-dispatch ceilin...
This record as markdown: /tools/app-lasers-guildcontrol-discord/plan-guild-prune.md
What plan_guild_prune does on GuildControl MCP
AI agents invoke plan_guild_prune to trigger actions in GuildControl MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why plan_guild_prune is rated High
Prepares and triggers a guild prune operation, kicking members from a Discord server.
From the tool's definition plan for one bounded non-exact Discord guild prune
Attacks that exploit this kind of access
The rule that runs plan_guild_prune 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_guild_prune, this is the rule to start with:
plan_guild_prune stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GuildControl MCP, apply this rule, and every plan_guild_prune call is checked against it from then on.
Questions about plan_guild_prune
Prepare a process-bound keyed plan for one bounded non-exact Discord guild prune. Verifies pinned identity, exact guild and include-role policy, complete KICK_MEMBERS plus MANAGE_GUILD evidence, safe role widening, protected-identity shields, a fresh native count estimate, two pre-dispatch ceilings, and the one-shot operation key without writing or claiming unavailable member IDs. It is categorised as a Execute tool in the GuildControl MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GuildControl MCP server in PolicyLayer and add a rule for plan_guild_prune: 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_guild_prune is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the plan_guild_prune 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_guild_prune. 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_guild_prune 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