AI agents call discord_get_scheduled_event 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 only queries and returns information about a scheduled Discord event without modifying, deleting, executing commands, or triggering external operations. The explicit 'Read-only' designation and retrieval-focused action confirm it falls squarely into the Read category with minimal security risk.
From the tool's definition Tool description explicitly states 'Read-only' and retrieves data: 'Get full details for one scheduled event: name, description, status, type, channel/location, start/end times, creator, and interested-user count. Returns a JSON object.'
Attacks that exploit this kind of access
Get full details for one scheduled event: name, description, status, type, channel/location, start/end times, creator, and interested-user count. Read-only. Returns a JSON object. 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_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 Discord. Nothing to install.
discord_get_scheduled_event 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_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.
Set action: deny in the PolicyLayer policy for discord_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.
discord_get_scheduled_event 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 →