create_booking
Create a new booking for a member. Use get_available_slots first to find valid times, then create the booking with the service, member, date, and time.
This record as markdown: /tools/io-favcrm-favcrm/create-booking.md
What create_booking does on FavCRM
AI agents use create_booking to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
notes | string | — | Booking notes |
endTime | string | Yes | End time in HH:MM format |
staffId | string | — | Staff member ID |
accountId | string | Yes | The member/account ID |
serviceId | string | Yes | The service ID |
startTime | string | Yes | Start time in HH:MM format |
resourceId | string | — | Resource ID |
bookingDate | string | Yes | Date in YYYY-MM-DD format |
Parameters from the server's own tool schema.
Why create_booking is rated Medium
This tool creates new business records (bookings) within a CRM system, which is a Write operation — it modifies data state reversibly. An AI agent misusing this could spam bookings, create fraudulent reservations, or disrupt service scheduling (medium severity). The tool requires valid service, member, date, and time parameters, limiting but not eliminating misuse risk.
From the tool's definition Tool name is 'create_booking' and description states it will 'Create a new booking' — a reversible data creation operation. The tool modifies system state by adding a new booking record but does not delete, execute arbitrary code, or move money.
Attacks that exploit this kind of access
The rule that runs create_booking safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_booking, this is the rule to start with:
create_booking stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every create_booking call is checked against it from then on.
Questions about create_booking
Create a new booking for a member. Use get_available_slots first to find valid times, then create the booking with the service, member, date, and time. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_booking accepts 8 parameters: notes, endTime, staffId, accountId, serviceId, startTime, resourceId, bookingDate. Required: endTime, accountId, serviceId, startTime, bookingDate. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM 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 FavCRM. 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 FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue