scheduling_book

SERVERServicialo SOURCE@servicialo/mcp-server

Medium RISK CLASS

Category Write

Parameters 84 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-servicialo-mcp-server/scheduling-book.md

WHAT IT DOES

What scheduling_book does on Servicialo

AI agents use scheduling_book 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
`notes`	string	—
`orgSlug`	string	Yes
`datetime`	string	Yes
`requester`	object	Yes
`service_id`	string	Yes
`submission`	object	—
`provider_id`	string	—
`idempotencyKey`	string	—

Parameters from the server's own tool schema.

RISK

Why scheduling_book is rated Medium

This tool creates a booking/reservation record using the requester's identity without requiring an API key. While the booking is not finalized until scheduling_confirm is called (suggesting some reversibility), it still commits a session slot and creates a booking_id.

From the tool's definition 'Book a session' and 'Returns confirmation_credential...and booking_id' and 'Does NOT require an API key — uses requester identity'

Risk signalsHigh parameter count (17 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scheduling_book 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_book, this is the rule to start with:

scheduling_book Rate-limited

scheduling_book 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scheduling_book": {
      "limits": [
        {
          "counter": "scheduling_book_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every scheduling_book call is checked against it from then on.

FAQ

Questions about scheduling_book

What does the scheduling_book tool do? +

Book a session (Servicialo spec). Returns confirmation_credential (opaque token, valid 30 min) and booking_id. Use scheduling_confirm with the credential to finalize. Does NOT require an API key — uses requester identity (fullName + email or phone). Accepts optional submission context for audit trail. 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.

What parameters does scheduling_book accept? +

scheduling_book accepts 8 parameters: notes, orgSlug, datetime, requester, service_id, submission, provider_id, idempotencyKey. Required: orgSlug, datetime, requester, service_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on scheduling_book? +

Register the Servicialo MCP server in PolicyLayer and add a rule for scheduling_book: 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.

What risk level is scheduling_book? +

scheduling_book is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit scheduling_book? +

Yes. Add a rate_limit block to the scheduling_book 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.

How do I block scheduling_book completely? +

Set action: deny in the PolicyLayer policy for scheduling_book. 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.

What MCP server provides scheduling_book? +

scheduling_book 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.

KEEP EXPLORING

More on Servicialo, and thousands of servers like it.

This server

All 111 Servicialo tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →