booking_update_status

SERVERServicialo SOURCE@servicialo/mcp-server

Medium RISK CLASS

Category Write

Parameters 73 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/booking-update-status.md

WHAT IT DOES

What booking_update_status does on Servicialo

AI agents use booking_update_status 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	—
`action`	string	Yes
`apiKey`	string	—
`orgSlug`	string	Yes
`sessionId`	string	Yes
`noShowType`	string	—
`deliveryType`	string	—

Parameters from the server's own tool schema.

RISK

Why booking_update_status is rated Medium

This tool creates or modifies booking/session data reversibly without permanent deletion. While it affects professional service delivery workflows and could cause business disruption if misused (confirming sessions the user shouldn't confirm, or marking sessions as no-show), the modifications are not destructive—they can be corrected by re-updating the status.

From the tool's definition Tool description states it can "advance a session through the Servicialo lifecycle: confirm, start, complete, or mark as no-show." These are state transitions that modify booking records reversibly.

Risk signalsHandles credentials or secrets (apiKey)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

booking_update_status Rate-limited

booking_update_status 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": {
    "booking_update_status": {
      "limits": [
        {
          "counter": "booking_update_status_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 booking_update_status call is checked against it from then on.

FAQ

Questions about booking_update_status

What does the booking_update_status tool do? +

Advance a session through the Servicialo lifecycle: confirm, start, complete, or mark as no-show. NOTE: the "deliver" action is NOT available via MCP (ref PDC-SEC-001) — MCP authentication cannot validate actor-as-Proveedor. Delivery must be performed via the REST endpoint PATCH /api/organizations/[orgSlug]/coordinalo/sessions/[sessionId]/deliver which enforces provider binding. 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 booking_update_status accept? +

booking_update_status accepts 7 parameters: notes, action, apiKey, orgSlug, sessionId, noShowType, deliveryType. Required: action, orgSlug, sessionId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on booking_update_status? +

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

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

Can I rate-limit booking_update_status? +

Yes. Add a rate_limit block to the booking_update_status 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 booking_update_status completely? +

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

booking_update_status 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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