public_availability_get_slots
Query available time slots for public booking. Does NOT require an API key. Returns slots grouped by service from the organization's public agenda. Provider details are hidden — the system auto-assigns at booking time. Use after public_service_list to find bookable times.
This record as markdown: /tools/com-servicialo-mcp-server/public-availability-get-slots.md
What public_availability_get_slots does on Servicialo
AI agents call public_availability_get_slots 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 |
|---|---|---|---|
date | string | — | |
dateTo | string | — | |
orgSlug | string | Yes | |
dateFrom | string | — | |
timezone | string | — | |
serviceId | string | — |
Parameters from the server's own tool schema.
Why public_availability_get_slots is rated Low
This tool retrieves and queries scheduling data without side effects. It does not create, modify, delete, or execute operations. The data returned (available time slots) is informational only, used to inform booking decisions made elsewhere. No irreversible changes, code execution, or financial transactions occur. This is a classic Read operation with minimal risk.
From the tool's definition Tool description states it 'Query[s] available time slots' and 'Returns slots grouped by service'. The verb 'Query' and 'Returns' indicate data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs public_availability_get_slots 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_availability_get_slots, this is the rule to start with:
public_availability_get_slots 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_availability_get_slots call is checked against it from then on.
Questions about public_availability_get_slots
Query available time slots for public booking. Does NOT require an API key. Returns slots grouped by service from the organization's public agenda. Provider details are hidden — the system auto-assigns at booking time. Use after public_service_list to find bookable times. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
public_availability_get_slots accepts 6 parameters: date, dateTo, orgSlug, dateFrom, timezone, serviceId. 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 public_availability_get_slots: 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_availability_get_slots 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_availability_get_slots 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_availability_get_slots. 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_availability_get_slots 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