List scheduled Calendly events with optional filters
AI agents call list_scheduled_events to retrieve information from Mcp Calendly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing calendar event data without modifying, deleting, or executing any external operations. It falls clearly into the Read category as a listing/query function. Severity is low because reading calendar events poses minimal risk; the blast radius of misuse would be limited to information disclosure of scheduling data already known to the account holder or their attendees.
From the tool's definition Tool name is 'list_scheduled_events' and description states 'List scheduled Calendly events with optional filters' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List scheduled Calendly events with optional filters. It is categorised as a Read tool in the Mcp Calendly MCP Server, which means it retrieves data without modifying state.
Register the Mcp Calendly 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 Mcp Calendly. Nothing to install.
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 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 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.
list_scheduled_events is provided by the Mcp Calendly MCP server (shwetank-dev/mcp-server-calendly). 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 →