booking_get
Get complete details of a session/appointment by its ID, including client, provider, service, financial, and delivery proof information.
This record as markdown: /tools/com-servicialo-mcp-server/booking-get.md
What booking_get does on Servicialo
AI agents call booking_get to retrieve information from Servicialo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
orgSlug | string | Yes | |
sessionId | string | Yes |
Parameters from the server's own tool schema.
Why booking_get is rated Low
This tool retrieves existing booking information by ID. While it accesses sensitive data (client, provider, service, financial details), it performs no side effects—no creation, modification, deletion, or execution. The risk is low because unauthorized reads are typically less severe than write or destructive operations, though access control on such data should still be enforced.
From the tool's definition Tool name 'booking_get' and description 'Get complete details of a session/appointment by its ID' indicate retrieval without modification. The verb 'Get' and the read-only nature of fetching appointment details confirm this is a query operation.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs booking_get 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_get, this is the rule to start with:
booking_get is read-only, so it stays allowed. 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 booking_get call is checked against it from then on.
Questions about booking_get
Get complete details of a session/appointment by its ID, including client, provider, service, financial, and delivery proof information. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
booking_get accepts 3 parameters: apiKey, orgSlug, sessionId. Required: 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_get: 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_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the booking_get 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_get. 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_get 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