booking_list
List sessions for an organization with filters by provider, client, service, status, and date range. Supports cursor-based pagination.
This record as markdown: /tools/com-servicialo-mcp-server/booking-list.md
What booking_list does on Servicialo
AI agents call booking_list 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 |
|---|---|---|---|
limit | integer | — | |
apiKey | string | — | |
cursor | string | — | |
dateTo | string | — | |
status | object | — | |
orderBy | string | — | |
orgSlug | string | Yes | |
clientId | string | — | |
dateFrom | string | — | |
serviceId | string | — | |
providerId | string | — |
Parameters from the server's own tool schema.
Why booking_list is rated Low
This tool retrieves and queries booking/session records with various filters and pagination support. It performs no creation, modification, deletion, or execution of external operations. The blast radius of misuse is limited to information disclosure of booking data, which is low severity.
From the tool's definition Tool name 'booking_list' and description 'List sessions for an organization with filters' — uses verb 'list' which retrieves data without side effects. Cursor-based pagination is characteristic of read operations.
Risk signalsHandles credentials or secrets (apiKey) · High parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs booking_list 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_list, this is the rule to start with:
booking_list 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_list call is checked against it from then on.
Questions about booking_list
List sessions for an organization with filters by provider, client, service, status, and date range. Supports cursor-based pagination. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
booking_list accepts 11 parameters: limit, apiKey, cursor, dateTo, status, orderBy, orgSlug, clientId, dateFrom, serviceId, providerId. 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 booking_list: 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_list 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_list 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_list. 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_list 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