plan_channel_metadata_change

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-channel-metadata-change.md

WHAT IT DOES

What plan_channel_metadata_change does on GuildControl MCP

AI agents use plan_channel_metadata_change 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_channel_metadata_change is rated Medium

Tool stages a channel metadata update plan without persisting changes; approval required before Write execution.

From the tool's definition Prepare a process-bound keyed plan for a partial metadata update to one exact separately allowlisted non-thread guild channel.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

plan_channel_metadata_change Rate-limited

plan_channel_metadata_change 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_channel_metadata_change": {
      "limits": [
        {
          "counter": "plan_channel_metadata_change_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_channel_metadata_change call is checked against it from then on.

FAQ

Questions about plan_channel_metadata_change

What does the plan_channel_metadata_change tool do? +

Prepare a process-bound keyed plan for a partial metadata update to one exact separately allowlisted non-thread guild channel. Verifies pinned application and bot identity, complete guild, member, role, overwrite, VIEW_CHANNEL, MANAGE_CHANNELS, and type-required CONNECT evidence, field applicability and bounds, boost-aware bitrate and user limits, explicit guild voice-region availability, omitted-field preservation, and current-to-desired changes without writing or persisting Discord text. 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_channel_metadata_change? +

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

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

Can I rate-limit plan_channel_metadata_change? +

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

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

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