booking_create
Create a new session/appointment for a client. providerId is optional — if omitted, the system auto-assigns a provider using the agenda assignment strategy (round_robin, least_booked, etc.). When a client has a titular provider, that provider is preferred automatically. Without providerId and wit...
This record as markdown: /tools/com-servicialo-mcp-server/booking-create.md
What booking_create does on Servicialo
AI agents use booking_create to create or update resources in Servicialo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Servicialo environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
notes | string | — | |
apiKey | string | — | |
orgSlug | string | Yes | |
clientId | string | Yes | |
duration | integer | — | |
modalidad | string | — | |
serviceId | string | Yes | |
autoCharge | boolean | — | |
providerId | string | — | |
retroactive | boolean | — | |
scheduledAt | string | Yes | |
idempotencyKey | string | — |
Parameters from the server's own tool schema.
Why booking_create is rated Medium
booking_create modifies persistent data by creating appointment records in the system. It is reversible (appointments can typically be cancelled or modified via other tools like agendas_delete or agendas_update on the same server), so it qualifies as Write rather than Destructive.
From the tool's definition Tool creates a new session/appointment; description states 'Create a new session/appointment for a client' and allows setting retroactive bookings, indicating irreversible creation of appointment records.
Risk signalsHandles credentials or secrets (apiKey) · High parameter count (14 properties)
Attacks that exploit this kind of access
The rule that runs booking_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Servicialo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For booking_create, this is the rule to start with:
booking_create 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 Servicialo, apply this rule, and every booking_create call is checked against it from then on.
Questions about booking_create
Create a new session/appointment for a client. providerId is optional — if omitted, the system auto-assigns a provider using the agenda assignment strategy (round_robin, least_booked, etc.). When a client has a titular provider, that provider is preferred automatically. Without providerId and without publicAgendaId, the org default public agenda is used. Preconditions: (1) service must exist and be active, (2) client must exist (use client_create first). Use availability_get_slots to find valid time slots before calling this. Set retroactive: true to register past sessions (skips slot validation, sets status to completed by default). Use autoCharge: true with retroactive to auto-generate the charge. Retroactive sessions are tagged with self_declared provenance. Max 365 days in the past. Past dates are auto-detected as retroactive — the retroactive flag is optional (system infers it from scheduledAt). It is categorised as a Write tool in the Servicialo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
booking_create accepts 12 parameters: notes, apiKey, orgSlug, clientId, duration, modalidad, serviceId, autoCharge, providerId, retroactive, scheduledAt, idempotencyKey. Required: orgSlug, clientId, serviceId, scheduledAt. The full parameter table on this page comes from the server's own tool schema.
Register the Servicialo MCP server in PolicyLayer and add a rule for booking_create: 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 Servicialo. Nothing to install.
booking_create 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 booking_create 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 booking_create. 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.
booking_create is provided by the Servicialo MCP server (@servicialo/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Servicialo, and thousands of servers like it.
This server
Across the catalogue