list_guild_templates
Audit one complete bounded Guild Template inventory for a separately allowlisted source guild. Continuity-stable Gateway and HTTP evidence labels the live channel structure as complete or visibility-bounded. Every raw code and use URL is replaced before result construction with an opaque process-...
This record as markdown: /tools/app-lasers-guildcontrol-discord/list-guild-templates.md
What list_guild_templates does on GuildControl MCP
AI agents call list_guild_templates 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.
Why list_guild_templates is rated Low
Retrieves template metadata with privacy safeguards, but exposes guild structure and risky permissions audit data.
From the tool's definition Audit one complete bounded Guild Template inventory, count-only structure, names/descriptions omitted.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs list_guild_templates 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_guild_templates, this is the rule to start with:
list_guild_templates is read-only, so it stays allowed. 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 list_guild_templates call is checked against it from then on.
Questions about list_guild_templates
Audit one complete bounded Guild Template inventory for a separately allowlisted source guild. Continuity-stable Gateway and HTTP evidence labels the live channel structure as complete or visibility-bounded. Every raw code and use URL is replaced before result construction with an opaque process-local HMAC reference. Names, descriptions, creator profiles, role and channel names, topics, icon hashes, serialized snapshots, and raw payloads are omitted. Returns count-only structure, risky-permission evidence, dirty state, complete MANAGE_GUILD authority, explicit snapshot limitations, and no persistent Discord content. It is categorised as a Read tool in the GuildControl MCP MCP Server, which means it retrieves data without modifying state.
Register the GuildControl MCP server in PolicyLayer and add a rule for list_guild_templates: 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.
list_guild_templates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_guild_templates 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 list_guild_templates. 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.
list_guild_templates 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