book_get_availability
List open appointment times for one service, grouped by day, with the business's timezone. Always present times to the user in that timezone. Each slot includes a canonical holdLabel and expiresNote; copy those exact values into book_hold_slot when the user chooses the slot.
This record as markdown: /tools/com-getcaboo-caboo/book-get-availability.md
What book_get_availability does on Caboo
AI agents call book_get_availability to retrieve information from Caboo 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 |
|---|---|---|---|
slug | string | Yes | The provider slug from search_providers or get_provider. |
partySize | integer | — | Number of people, when the user states one and the service supports it. |
serviceKey | string | Yes | The service key from book_list_services. |
Parameters from the server's own tool schema.
Why book_get_availability is rated Low
This is a straightforward read operation that retrieves appointment availability information. It returns structured data (time slots grouped by day, timezone info, holdLabel, expiresNote) for display purposes. While it mentions values to be used in subsequent book_hold_slot calls, this tool itself performs no booking action—it only lists existing slots.
From the tool's definition Tool description explicitly states 'List open appointment times' and 'Always present times to the user'. The tool queries and retrieves availability data without modifying, creating, or deleting anything. No side effects or state changes occur.
Attacks that exploit this kind of access
The rule that runs book_get_availability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Caboo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For book_get_availability, this is the rule to start with:
book_get_availability 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 Caboo, apply this rule, and every book_get_availability call is checked against it from then on.
Questions about book_get_availability
List open appointment times for one service, grouped by day, with the business's timezone. Always present times to the user in that timezone. Each slot includes a canonical holdLabel and expiresNote; copy those exact values into book_hold_slot when the user chooses the slot. It is categorised as a Read tool in the Caboo MCP Server, which means it retrieves data without modifying state.
book_get_availability accepts 3 parameters: slug, partySize, serviceKey. Required: slug, serviceKey. The full parameter table on this page comes from the server's own tool schema.
Register the Caboo MCP server in PolicyLayer and add a rule for book_get_availability: 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 Caboo. Nothing to install.
book_get_availability 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 book_get_availability 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 book_get_availability. 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.
book_get_availability is provided by the Caboo MCP server (https://getcaboo.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Caboo, and thousands of servers like it.
This server
Across the catalogue