public_booking_get
Get details of a public booking using the bookingToken returned by public_booking_create. Returns status, scheduled time, service, and requester info. Does NOT require an API key — the booking token is the credential. Only returns public-safe data.
This record as markdown: /tools/com-servicialo-mcp-server/public-booking-get.md
What public_booking_get does on Servicialo
AI agents call public_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 |
|---|---|---|---|
orgSlug | string | Yes | |
bookingToken | string | Yes |
Parameters from the server's own tool schema.
Why public_booking_get is rated Low
This is fundamentally a Read operation—it retrieves and queries booking data without creating, modifying, or deleting anything. However, severity is elevated from low to medium because the tool uses a token-based access model rather than standard authentication, creating a moderate risk if a token is leaked or guessed.
From the tool's definition Tool description states it 'Get details of a public booking' and 'Returns status, scheduled time, service, and requester info.' These are retrieval operations with no data modification. However, the tool accepts a bookingToken as the sole credential mechanism.
Attacks that exploit this kind of access
The rule that runs public_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 public_booking_get, this is the rule to start with:
public_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 public_booking_get call is checked against it from then on.
Questions about public_booking_get
Get details of a public booking using the bookingToken returned by public_booking_create. Returns status, scheduled time, service, and requester info. Does NOT require an API key — the booking token is the credential. Only returns public-safe data. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
public_booking_get accepts 2 parameters: orgSlug, bookingToken. Required: orgSlug, bookingToken. 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 public_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.
public_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 public_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 public_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.
public_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