create_booking
AI agents use create_booking to create or update resources in Cal Com MCP Server for Customers — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cal Com MCP Server for Customers environment.
This tool creates calendar bookings, which are new data records in Cal.com. This is reversible (bookings can be cancelled or modified), so it falls under Write rather than Destructive. Severity is high because a compromised AI agent could spam bookings, create fraudulent appointments on behalf of the user, or cause calendar chaos affecting both the user and invitees.
From the tool's definition Tool name 'create_booking' combined with server description stating it 'enables AI assistants to book meetings' and 'manage Cal.com scheduling'. The tool description is empty, but the sibling context and tool name clearly indicate data creation.
Attacks that exploit this kind of access
create_booking. It is categorised as a Write tool in the Cal Com MCP Server for Customers MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cal Com MCP Server for Customers MCP server in PolicyLayer and add a rule for create_booking: 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.
create_booking is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_booking 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 create_booking. 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.
create_booking 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 →