update_booking_settings
Update global booking settings. Pass only the fields you want to change.
This record as markdown: /tools/io-favcrm-favcrm/update-booking-settings.md
What update_booking_settings does on FavCRM
AI agents use update_booking_settings 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 |
|---|---|---|---|
showCoupon | boolean | — | Show coupon field in booking flow |
calendarStyle | string | — | Booking flow calendar presentation |
showAccessPass | boolean | — | Show access pass/package options in booking flow |
cooldownMessage | object | — | Optional message shown when cooldown blocks a booking |
blockUntilFinished | boolean | — | Block customers from booking again while they have active bookings |
globalCooldownDays | object | — | Minimum days between customer bookings, or null to disable |
bookingReminderEnabled | boolean | — | Send the default pre-booking reminder |
sameDayReminderEnabled | boolean | — | Send an additional same-day reminder before booking start |
allowMemberCancellation | boolean | — | Allow members to cancel bookings from the customer portal |
bookingReminderLeadHours | integer | — | Hours before booking start for the default reminder |
hideUnavailableTimeslots | boolean | — | Hide unavailable timeslots instead of showing them as full |
sameDayReminderLeadHours | integer | — | Hours before booking start for the same-day reminder |
Parameters from the server's own tool schema.
Why update_booking_settings is rated Medium
This tool modifies booking configuration settings for the service business. While changes are reversible (can be updated again), they affect system-wide booking behavior and could impact customer-facing functionality if misconfigured. The blast radius is moderate—misuse could disrupt booking workflows but is not destructive or financial in nature.
From the tool's definition Tool name 'update_booking_settings' and description 'Update global booking settings' indicate modification of data. The phrase 'Pass only the fields you want to change' confirms reversible updates rather than deletion.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs update_booking_settings 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 update_booking_settings, this is the rule to start with:
update_booking_settings 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 update_booking_settings call is checked against it from then on.
Questions about update_booking_settings
Update global booking settings. Pass only the fields you want to change. 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.
update_booking_settings accepts 12 parameters: showCoupon, calendarStyle, showAccessPass, cooldownMessage, blockUntilFinished, globalCooldownDays, bookingReminderEnabled, sameDayReminderEnabled, allowMemberCancellation, bookingReminderLeadHours, hideUnavailableTimeslots, sameDayReminderLeadHours. 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 update_booking_settings: 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.
update_booking_settings 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 update_booking_settings 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 update_booking_settings. 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.
update_booking_settings 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