list_stage_instances

SERVERGuildControl MCP SOURCEguildctl

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/app-lasers-guildcontrol-discord/list-stage-instances.md

WHAT IT DOES

What list_stage_instances does on GuildControl MCP

AI agents call list_stage_instances to retrieve information from GuildControl MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_stage_instances is rated Low

Tool retrieves Discord Stage channel metadata without modifying data or enabling side effects.

From the tool's definition Inspect, returns state, scheduled-event linkage, no data persisted

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_stage_instances Allowed

list_stage_instances is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_stage_instances": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about list_stage_instances

What does the list_stage_instances tool do? +

Inspect every separately allowlisted Discord Stage channel as a bounded configured inventory. Returns exact active or inactive state, guild-only or deprecated-public privacy, scheduled-event linkage, schema-drift count, and complete read-permission evidence without speaker, audience, or raw payload data. Nothing is persisted. It is categorised as a Read tool in the GuildControl MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_stage_instances? +

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

list_stage_instances is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_stage_instances? +

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

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

list_stage_instances 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →