AI agents call discord_list_scheduled_events to retrieve information from Discord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves scheduled event metadata without modifying, deleting, or executing any operations. It is purely informational and has no side effects. The explicit 'Read-only' designation confirms it belongs in the Read category with low severity since listing events poses minimal security risk.
From the tool's definition The tool description explicitly states 'Read-only' and specifies that it 'List all scheduled events in a server' retrieving informational fields (id, name, status, type, time, location, interested count) with no modification capability.
Attacks that exploit this kind of access
List all scheduled events in a server (id, name, status, type, time, location, interested count). Read-only. Use discord_get_scheduled_event for one event. It is categorised as a Read tool in the Discord MCP Server, which means it retrieves data without modifying state.
Register the Discord MCP server in PolicyLayer and add a rule for discord_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 Discord. Nothing to install.
discord_list_scheduled_events 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 discord_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.
Set action: deny in the PolicyLayer policy for discord_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.
discord_list_scheduled_events is provided by the Discord MCP server (@pasympa/discord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →