calendly_list_event_types
AI agents call calendly_list_event_types 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.
The 'list' prefix strongly suggests this tool queries and retrieves a set of Calendly event types without side effects. No data is created, modified, deleted, or executed. While the description is uninformative, the consistent naming convention across the server and the explicit 'list' verb provide sufficient confidence that this is a simple read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'calendly_list_event_types' with 'list' verb indicates retrieval of event type data without modification.
Attacks that exploit this kind of access
calendly_list_event_types. 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_event_types: 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_event_types 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_event_types 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_event_types. 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_event_types 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 →