Lists appointments from Cal.com calendar.
AI agents call calcom_list_appointments to retrieve information from Cal Com Calendar MCP Server 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 retrieves existing calendar appointments without creating, modifying, or deleting any data. It has no side effects and presents minimal risk even if misused by an AI agent, as it only exposes read-only access to calendar information.
From the tool's definition Tool name 'calcom_list_appointments' and description 'Lists appointments from Cal.com calendar' indicate pure retrieval of calendar data with no modification or deletion.
Attacks that exploit this kind of access
Lists appointments from Cal.com calendar. It is categorised as a Read tool in the Cal Com Calendar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cal Com Calendar MCP Server MCP server in PolicyLayer and add a rule for calcom_list_appointments: 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 Calendar MCP Server. Nothing to install.
calcom_list_appointments 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 calcom_list_appointments 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 calcom_list_appointments. 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.
calcom_list_appointments is provided by the Cal Com Calendar MCP Server MCP server (mumunha/cal_dot_com_mcpserver). 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 →