public_booking_cancel
Cancel a public booking using the bookingToken. Only works for bookings in pending_confirmation, scheduled, or confirmed status. Optionally include a reason. Does NOT require an API key. The booking token scopes access to a single booking.
This record as markdown: /tools/com-servicialo-mcp-server/public-booking-cancel.md
What public_booking_cancel does on Servicialo
AI agents call public_booking_cancel to permanently remove resources in Servicialo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | |
orgSlug | string | Yes | |
bookingToken | string | Yes |
Parameters from the server's own tool schema.
Why public_booking_cancel is rated Critical
Cancelling a booking is an irreversible action that terminates a scheduled service appointment. While it may be possible to re-book, the original booking slot and its state are permanently destroyed. The tool requires no API key, meaning any agent with a bookingToken can cancel bookings — raising the blast radius significantly.
From the tool's definition Cancel a public booking... Only works for bookings in pending_confirmation, scheduled, or confirmed status
Attacks that exploit this kind of access
The rule that runs public_booking_cancel 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_cancel, this is the rule to start with:
public_booking_cancel is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every public_booking_cancel call is checked against it from then on.
Questions about public_booking_cancel
Cancel a public booking using the bookingToken. Only works for bookings in pending_confirmation, scheduled, or confirmed status. Optionally include a reason. Does NOT require an API key. The booking token scopes access to a single booking. It is categorised as a Destructive tool in the Servicialo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
public_booking_cancel accepts 3 parameters: reason, orgSlug, bookingToken. Required: orgSlug, bookingToken. 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_cancel: 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_cancel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the public_booking_cancel 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_cancel. 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_cancel 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.
Across the catalogue