New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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...

SERVERGuildControl MCP SOURCEguildctl
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about plan_guild_prune

What does the plan_guild_prune tool do? +

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.

How do I enforce a policy on plan_guild_prune? +

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.

What risk level is plan_guild_prune? +

plan_guild_prune is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit plan_guild_prune? +

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.

How do I block plan_guild_prune completely? +

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.

What MCP server provides plan_guild_prune? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GuildControl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.