plan_poll_end

SERVERGuildControl MCP SOURCEguildctl

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/app-lasers-guildcontrol-discord/plan-poll-end.md

WHAT IT DOES

What plan_poll_end does on GuildControl MCP

AI agents call plan_poll_end 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.

RISK

Why plan_poll_end is rated Critical

Ending a poll is irreversible; votes and poll lifecycle are permanently terminated.

From the tool's definition irreversibly end one exact bot-authored native Discord poll

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs plan_poll_end 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_poll_end, this is the rule to start with:

plan_poll_end Hidden

plan_poll_end is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "plan_poll_end"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GuildControl MCP, apply this rule, and every plan_poll_end call is checked against it from then on.

FAQ

Questions about plan_poll_end

What does the plan_poll_end tool do? +

Prepare a process-bound keyed plan to irreversibly end one exact bot-authored native Discord poll in a separately allowlisted channel. Verifies application and bot identity, exact guild, channel, ownership, lifecycle, future-field, permission, question, answer-ID, and live count evidence plus a unique one-shot operation key without writing or persisting poll content. 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.

How do I enforce a policy on plan_poll_end? +

Register the GuildControl MCP server in PolicyLayer and add a rule for plan_poll_end: 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_poll_end? +

plan_poll_end is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit plan_poll_end? +

Yes. Add a rate_limit block to the plan_poll_end 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_poll_end completely? +

Set action: deny in the PolicyLayer policy for plan_poll_end. 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_poll_end? +

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

KEEP EXPLORING

More on GuildControl, and thousands of servers like it.

This server

All 258 GuildControl tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →