book_get_booking_status
Check what happened to a held slot: still held, confirmed by the user, or expired. Call this when the user says they finished on the confirmation page (or asks whether it went through) so you can confirm the booking in the conversation. Returns no personal details.
This record as markdown: /tools/com-getcaboo-caboo/book-get-booking-status.md
What book_get_booking_status does on Caboo
AI agents call book_get_booking_status 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. |
holdToken | string | — | The token from the confirmUrl path, if you kept it. |
confirmUrl | string | — | The confirmUrl returned by book_hold_slot; the token is read from it. |
Parameters from the server's own tool schema.
Why book_get_booking_status is rated Low
This tool retrieves status information about a previously created booking hold without modifying, executing external operations, destroying data, or moving money. It is a read-only query operation with minimal blast radius if misused by an AI agent, as it only exposes non-personal booking status data.
From the tool's definition Tool description states it 'Check[s] what happened to a held slot' and 'Returns no personal details.' The action is purely informational—querying the status of an existing booking hold.
Attacks that exploit this kind of access
The rule that runs book_get_booking_status 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_booking_status, this is the rule to start with:
book_get_booking_status 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_booking_status call is checked against it from then on.
Questions about book_get_booking_status
Check what happened to a held slot: still held, confirmed by the user, or expired. Call this when the user says they finished on the confirmation page (or asks whether it went through) so you can confirm the booking in the conversation. Returns no personal details. It is categorised as a Read tool in the Caboo MCP Server, which means it retrieves data without modifying state.
book_get_booking_status accepts 3 parameters: slug, holdToken, confirmUrl. Required: slug. 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_booking_status: 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_booking_status 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_booking_status 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_booking_status. 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_booking_status 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