# 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.

Agent View of the PolicyLayer registry record for `book_get_booking_status`. HTML page: https://policylayer.com/tools/com-getcaboo-caboo/book-get-booking-status

## Facts

- Tool: `book_get_booking_status`
- Server: Caboo (`https://getcaboo.com/mcp`) — https://policylayer.com/tools/com-getcaboo-caboo.md
- Homepage: https://github.com/https://getcaboo.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `slug` | string | yes | The provider slug from search_providers or get_provider. |
| `holdToken` | string | no | The token from the confirmUrl path, if you kept it. |
| `confirmUrl` | string | no | The confirmUrl returned by book_hold_slot; the token is read from it. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "book_get_booking_status",
    "arguments": {
      "slug": "<slug>"
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Caboo:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "book_get_booking_status": {}
  }
}
```

## Other tools on Caboo (5)

- `book_get_availability` — Read — https://policylayer.com/tools/com-getcaboo-caboo/book-get-availability.md
- `book_list_services` — Read — https://policylayer.com/tools/com-getcaboo-caboo/book-list-services.md
- `get_provider` — Read — https://policylayer.com/tools/com-getcaboo-caboo/get-provider.md
- `search_providers` — Read — https://policylayer.com/tools/com-getcaboo-caboo/search-providers.md
- `book_hold_slot` — Write — https://policylayer.com/tools/com-getcaboo-caboo/book-hold-slot.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-getcaboo-caboo · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-getcaboo-caboo