plan_role_order
Prepare a process-bound keyed plan to place one exact standard Discord role immediately above or below one exact anchor role in a separately allowlisted guild. Verifies pinned application and bot identity, complete guild, member, role-inventory, canonical hierarchy, MANAGE_ROLES, aggregate holder...
This record as markdown: /tools/app-lasers-guildcontrol-discord/plan-role-order.md
What plan_role_order does on GuildControl MCP
AI agents use plan_role_order 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.
Why plan_role_order is rated Medium
An AI agent can call plan_role_order faster than any human can review: one bad instruction and it creates or modifies resources in GuildControl MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs plan_role_order 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_role_order, this is the rule to start with:
plan_role_order 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.
The button opens the PolicyLayer dashboard: create your workspace, connect GuildControl MCP, apply this rule, and every plan_role_order call is checked against it from then on.
Questions about plan_role_order
Prepare a process-bound keyed plan to place one exact standard Discord role immediately above or below one exact anchor role in a separately allowlisted guild. Verifies pinned application and bot identity, complete guild, member, role-inventory, canonical hierarchy, MANAGE_ROLES, aggregate holder counts, managed and connector-held boundaries, affected hierarchy-sensitive permissions, and unknown future fields without writing or persistence. 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.
Register the GuildControl MCP server in PolicyLayer and add a rule for plan_role_order: 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_role_order is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the plan_role_order 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_role_order. 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_role_order 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.
This server
Across the catalogue