list_scheduled_events

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-scheduled-events.md

WHAT IT DOES

What list_scheduled_events does on GuildControl MCP

AI agents call list_scheduled_events 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_scheduled_events is rated Low

Tool retrieves event data with privacy safeguards and no side effects or persistence.

From the tool's definition List complete scheduled-event inventory, privacy-safe metadata, read-permission evidence, nothing persisted.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_scheduled_events Allowed

list_scheduled_events 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_scheduled_events": {}
  }
}

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

FAQ

Questions about list_scheduled_events

What does the list_scheduled_events tool do? +

List the complete bounded scheduled-event inventory for one separately allowlisted Discord guild. Returns privacy-safe event metadata and complete entity-specific read-permission evidence. Aggregate subscriber counts are opt-in; subscriber identities, creator profiles, cover URLs and hashes, and unknown raw fields are omitted. 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_scheduled_events? +

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

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

Can I rate-limit list_scheduled_events? +

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

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

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