public_booking_confirm
Confirm a pending public booking using the confirmationToken returned by public_booking_create. Advances the booking from pending_confirmation to scheduled. The token expires after 30 minutes. Does NOT require an API key. Rate-limited.
This record as markdown: /tools/com-servicialo-mcp-server/public-booking-confirm.md
What public_booking_confirm does on Servicialo
AI agents use public_booking_confirm 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 |
|---|---|---|---|
orgSlug | string | Yes | |
confirmationToken | string | Yes |
Parameters from the server's own tool schema.
Why public_booking_confirm is rated Medium
This tool transitions a booking from a pending state to a scheduled state, which is a reversible write operation (bookings can presumably be cancelled). It does not delete data, execute arbitrary code, or move money directly, though it does commit a service appointment.
From the tool's definition Confirm a pending public booking...Advances the booking from pending_confirmation to scheduled
Attacks that exploit this kind of access
The rule that runs public_booking_confirm 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_confirm, this is the rule to start with:
public_booking_confirm 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_confirm call is checked against it from then on.
Questions about public_booking_confirm
Confirm a pending public booking using the confirmationToken returned by public_booking_create. Advances the booking from pending_confirmation to scheduled. The token expires after 30 minutes. Does NOT require an API key. Rate-limited. 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_confirm accepts 2 parameters: orgSlug, confirmationToken. Required: orgSlug, confirmationToken. 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_confirm: 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_confirm 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_confirm 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_confirm. 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_confirm 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