get_scheduled_event

Get one exact scheduled event from a separately allowlisted Discord guild with complete entity-specific read-permission evidence. The aggregate subscriber count is opt-in; subscriber identities, creator profiles, cover URLs and hashes, and unknown raw fields are omitted. Nothing is persisted.

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/get-scheduled-event.md

WHAT IT DOES

What get_scheduled_event does on GuildControl MCP

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

Retrieves event data with privacy controls; no modifications, side effects, or persistence.

From the tool's definition Get one exact scheduled event, read-permission, subscriber count opt-in, nothing persisted

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_scheduled_event Allowed

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

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

FAQ

Questions about get_scheduled_event

What does the get_scheduled_event tool do? +

How do I enforce a policy on get_scheduled_event? +

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

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

Can I rate-limit get_scheduled_event? +

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

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

get_scheduled_event 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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