booking_cancel
Cancel an existing session. By default applies the org cancellation policy: the charge is computed from the no-charge/partial/full windows and, if the policy has autoApply, registered as a penalty transaction (money-write). Set applyCancellationPolicy: false to waive the charge. Requires confirm:...
This record as markdown: /tools/com-servicialo-mcp-server/booking-cancel.md
What booking_cancel does on Servicialo
AI agents use booking_cancel to commit financial operations through Servicialo, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
reason | string | Yes | |
confirm | boolean | Yes | |
orgSlug | string | Yes | |
sessionId | string | Yes | |
cancelledBy | string | — | |
applyCancellationPolicy | boolean | — |
Parameters from the server's own tool schema.
Why booking_cancel is rated Critical
This tool cancels a booking and by default triggers a financial penalty transaction based on the cancellation policy. It directly commits financial obligations (penalty charges) against a party, placing it firmly in the Financial category. The irreversible nature of the financial transaction and the potential for incorrect charges (or wrongful waivers via applyCancellationPolicy:false) make the blast radius critical.
From the tool's definition 'the charge is computed from the no-charge/partial/full windows and, if the policy has autoApply, registered as a penalty transaction (money-write)'
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs 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 booking_cancel, this is the rule to start with:
Any call to booking_cancel is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every booking_cancel call is checked against it from then on.
Questions about booking_cancel
Cancel an existing session. By default applies the org cancellation policy: the charge is computed from the no-charge/partial/full windows and, if the policy has autoApply, registered as a penalty transaction (money-write). Set applyCancellationPolicy: false to waive the charge. Requires confirm: true. It is categorised as a Financial tool in the Servicialo MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
booking_cancel accepts 7 parameters: apiKey, reason, confirm, orgSlug, sessionId, cancelledBy, applyCancellationPolicy. Required: reason, confirm, orgSlug, sessionId. 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_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.
booking_cancel is a Financial 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 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 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.
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