scheduling_cancel
Cancel a session through the Servicialo protocol lane. Moves the session to cancelled and emits sc_service.cancelled.v1. It REPORTS the cancellation policy tier that applies (policy_applied: none | partial | full, with the percentage) but does NOT create any charge — no penalty transaction is per...
This record as markdown: /tools/com-servicialo-mcp-server/scheduling-cancel.md
What scheduling_cancel does on Servicialo
AI agents use scheduling_cancel 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 |
|---|---|---|---|
apiKey | string | — | |
reason | string | — | |
confirm | boolean | Yes | |
orgSlug | string | Yes | |
session_id | string | Yes |
Parameters from the server's own tool schema.
Why scheduling_cancel is rated Medium
Cancels a session reversibly (no charge), modifying session state without financial or destructive impact.
From the tool's definition Moves the session to cancelled and emits sc_service.cancelled.v1
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs scheduling_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 scheduling_cancel, this is the rule to start with:
scheduling_cancel 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 scheduling_cancel call is checked against it from then on.
Questions about scheduling_cancel
Cancel a session through the Servicialo protocol lane. Moves the session to cancelled and emits sc_service.cancelled.v1. It REPORTS the cancellation policy tier that applies (policy_applied: none | partial | full, with the percentage) but does NOT create any charge — no penalty transaction is persisted and the client owes nothing as a result of this call. If you need the organization lane that actually applies the policy and registers the charge, use booking_cancel instead. Requires confirm: true and X-Org-Api-Key. 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.
scheduling_cancel accepts 5 parameters: apiKey, reason, confirm, orgSlug, session_id. Required: confirm, orgSlug, session_id. 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 scheduling_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.
scheduling_cancel 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 scheduling_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 scheduling_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.
scheduling_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.
This server
Across the catalogue