scheduling_confirm
Confirm a booking (Servicialo spec). Dual-mode: (1) with credential — uses the confirmation token from scheduling_book, no API key needed; (2) with booking_id — uses API key to confirm an existing session. Returns confirmed status with timestamp.
This record as markdown: /tools/com-servicialo-mcp-server/scheduling-confirm.md
What scheduling_confirm does on Servicialo
AI agents use scheduling_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 |
|---|---|---|---|
apiKey | string | — | |
orgSlug | string | Yes | |
booking_id | string | — | |
credential | string | — |
Parameters from the server's own tool schema.
Why scheduling_confirm is rated Medium
Confirming a booking is a Write operation: it changes the state of an existing booking record from pending to confirmed. While it triggers a real-world service commitment, it does not move money directly (that would be Financial), does not execute arbitrary code (Execute), and is not irreversible in the same sense as deletion (Destructive).
From the tool's definition 'Confirm a booking' and 'Returns confirmed status with timestamp' — the tool commits/finalizes a booking session, creating a confirmed state from a pending one.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs scheduling_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 scheduling_confirm, this is the rule to start with:
scheduling_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 scheduling_confirm call is checked against it from then on.
Questions about scheduling_confirm
Confirm a booking (Servicialo spec). Dual-mode: (1) with credential — uses the confirmation token from scheduling_book, no API key needed; (2) with booking_id — uses API key to confirm an existing session. Returns confirmed status with timestamp. 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_confirm accepts 4 parameters: apiKey, orgSlug, booking_id, credential. Required: orgSlug. 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_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.
scheduling_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 scheduling_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 scheduling_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.
scheduling_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