list_event_types
AI agents call list_event_types to retrieve information from Cal Com MCP Server for Customers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' verb and '_event_types' noun pattern indicate retrieval of event type definitions without modification. Within a Cal.com scheduling context, this would query available meeting types. No side effects, mutations, or external operations are implied. Empty description slightly reduces confidence, but tool naming and server purpose strongly suggest this is a simple read operation.
From the tool's definition Tool name 'list_event_types' combined with server context of booking/scheduling management indicates data retrieval. Description is empty, but naming convention and sibling tools (get_bookings, get_api_status) suggest read-only query operation.
Attacks that exploit this kind of access
list_event_types. It is categorised as a Read tool in the Cal Com MCP Server for Customers MCP Server, which means it retrieves data without modifying state.
Register the Cal Com MCP Server for Customers MCP server in PolicyLayer and add a rule for 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 Cal Com MCP Server for Customers. Nothing to install.
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 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 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.
list_event_types is provided by the Cal Com MCP Server for Customers MCP server (niopub/calcom-mcp-for-customers). 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 →