plan_invite_creation

SERVERGuildControl MCP SOURCEguildctl

Medium RISK CLASS

Category Write

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-invite-creation.md

WHAT IT DOES

What plan_invite_creation does on GuildControl MCP

AI agents use plan_invite_creation to create or update resources in GuildControl MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GuildControl MCP environment.

RISK

Why plan_invite_creation is rated Medium

Creates a reversible Discord invite with optional role assignment; does not execute or delete, but modifies guild state through planned permission changes.

From the tool's definition Prepare a process-bound plan to create one finite unique Discord invite with explicit bearer or exact-user acceptance and optional separately gated persistent role assignment

Attacks that exploit this kind of access

RECOMMENDED RULE

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

plan_invite_creation Rate-limited

plan_invite_creation stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "plan_invite_creation": {
      "limits": [
        {
          "counter": "plan_invite_creation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_invite_creation call is checked against it from then on.

FAQ

Questions about plan_invite_creation

What does the plan_invite_creation tool do? +

Prepare a process-bound keyed plan to create one finite unique Discord invite with explicit bearer or exact-user acceptance and optional separately gated persistent role assignment in an allowlisted direct guild channel. Verifies pinned identity, complete guild, member, role, channel, overwrite, VIEW_CHANNEL, and CREATE_INSTANT_INVITE evidence; conditional MANAGE_GUILD and MANAGE_ROLES authority; role hierarchy, permission subset, minimum new-member channel impact, and an absent canonical private output target, without creating a capability or file. It is categorised as a Write tool in the GuildControl MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on plan_invite_creation? +

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

plan_invite_creation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit plan_invite_creation? +

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

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

plan_invite_creation 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 →

Across the catalogue

poc_plan on 05 Mcp A2a Solution Studio →emit_variant_plan on 0sec → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →