# get_quote

Exact per-vehicle prices from the live fixed price list — airport transfers (OOL/BNE) and Brisbane Cruise Terminal runs (use "Brisbane Cruise Terminal" or "Pinkenba" as the place). Deterministic — never estimates. If match is "none", give the customer the phone number instead of guessing.

Agent View of the PolicyLayer registry record for `get_quote`. HTML page: https://policylayer.com/tools/com-gc-airporttransfers-booking/get-quote

## Facts

- Tool: `get_quote`
- Server: Booking (`https://gc-airporttransfers.com/wp-json/atb-gateway/v1/mcp`) — https://policylayer.com/tools/com-gc-airporttransfers-booking.md
- Homepage: https://github.com/https://gc-airporttransfers.com/wp-json/atb-gateway/v1/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 5 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `to` | string | yes | Drop-off place, e.g. "Gold Coast Airport" or a suburb |
| `pax` | integer | no | Passengers 1-11 (filters vehicles) |
| `date` | string | no | YYYY-MM-DD (optional) |
| `from` | string | yes | Pick-up place, e.g. "Broadbeach" or "OOL" |
| `time` | string | no | HH:MM 24h (optional; flags after-hours surcharge) |

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": "get_quote",
    "arguments": {
      "to": "<to>",
      "from": "<from>"
    }
  }
}
```

## Why get_quote is rated Low

Even though get_quote only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call get_quote to retrieve information from Booking 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 Booking:

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

## Other tools on Booking (3)

- `check_availability` — Read — https://policylayer.com/tools/com-gc-airporttransfers-booking/check-availability.md
- `get_service_info` — Read — https://policylayer.com/tools/com-gc-airporttransfers-booking/get-service-info.md
- `request_booking` — Read — https://policylayer.com/tools/com-gc-airporttransfers-booking/request-booking.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-gc-airporttransfers-booking · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gc-airporttransfers-booking