calendly_list_scheduled_events
AI agents call calendly_list_scheduled_events to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves scheduled events from Calendly without modifying, deleting, or executing any actions. The 'list' operation pattern is standard for read operations. Although the description is empty, the tool name itself strongly suggests querying calendar event data.
From the tool's definition Tool name 'calendly_list_scheduled_events' indicates a list/query operation with no apparent side effects. The verb 'list' is characteristic of read-only retrieval operations.
Attacks that exploit this kind of access
calendly_list_scheduled_events. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for calendly_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 Integrations MCP. Nothing to install.
calendly_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 calendly_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 calendly_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.
calendly_list_scheduled_events is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →