public_booking_create
Create a public booking request. Does NOT require an API key, but DOES require: (1) requester identity — fullName plus at least email or phone, (2) submission context — channel and whether an agent assisted, (3) authorization.humanIntentConfirmed must be true. The booking is created as pending_co...
This record as markdown: /tools/com-servicialo-mcp-server/public-booking-create.md
What public_booking_create does on Servicialo
AI agents use public_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 | — | |
orgSlug | string | Yes | |
startAt | string | Yes | |
requester | object | Yes | |
serviceId | string | Yes | |
submission | object | Yes | |
authorization | object | Yes | |
idempotencyKey | string | — |
Parameters from the server's own tool schema.
Why public_booking_create is rated Medium
This is a Write operation because it creates new data (a booking record) and the effect is reversible via the returned bookingToken (cancel/reschedule). It does not execute arbitrary code (Execute) or permanently delete data (Destructive). While it requires authorization.humanIntentConfirmed and is rate-limited, these are guardrails rather than indicators of higher severity.
From the tool's definition 'Create a public booking request' — the tool creates a new booking record in pending_confirmation state. Returns bookingToken for lifecycle management (cancel, reschedule), indicating reversible state mutation.
Risk signalsHigh parameter count (20 properties)
Attacks that exploit this kind of access
The rule that runs public_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 public_booking_create, this is the rule to start with:
public_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 public_booking_create call is checked against it from then on.
Questions about public_booking_create
Create a public booking request. Does NOT require an API key, but DOES require: (1) requester identity — fullName plus at least email or phone, (2) submission context — channel and whether an agent assisted, (3) authorization.humanIntentConfirmed must be true. The booking is created as pending_confirmation — use public_booking_confirm with the returned confirmationToken to confirm. A bookingToken is also returned for future lifecycle management (cancel, reschedule). Rate-limited per IP+org. All requests are audited with semantic decision codes. Use public_service_list → public_availability_get_slots → public_booking_create → public_booking_confirm as the complete public booking flow. 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.
public_booking_create accepts 8 parameters: notes, orgSlug, startAt, requester, serviceId, submission, authorization, idempotencyKey. Required: orgSlug, startAt, requester, serviceId, submission, authorization. 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 public_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.
public_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 public_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 public_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.
public_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