check_availability
Whether a pick-up date/time is bookable under standard operating rules (not a live calendar). Standard hours 06:00-21:00 AEST; outside that is an after-hours request; same-day should phone.
This record as markdown: /tools/com-gc-airporttransfers-booking/check-availability.md
What check_availability does on Booking
AI agents call check_availability 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | Yes | YYYY-MM-DD |
time | string | Yes | HH:MM 24h |
Parameters from the server's own tool schema.
Why check_availability is rated Low
Even though check_availability 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.
Attacks that exploit this kind of access
The rule that runs check_availability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Booking, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_availability, this is the rule to start with:
check_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 Booking, apply this rule, and every check_availability call is checked against it from then on.
Questions about check_availability
Whether a pick-up date/time is bookable under standard operating rules (not a live calendar). Standard hours 06:00-21:00 AEST; outside that is an after-hours request; same-day should phone. It is categorised as a Read tool in the Booking MCP Server, which means it retrieves data without modifying state.
check_availability accepts 2 parameters: date, time. Required: date, time. The full parameter table on this page comes from the server's own tool schema.
Register the Booking MCP server in PolicyLayer and add a rule for check_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 Booking. Nothing to install.
check_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 check_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 check_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.
check_availability is provided by the Booking MCP server (https://gc-airporttransfers.com/wp-json/atb-gateway/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Booking, and thousands of servers like it.
This server
Across the catalogue