New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

request_booking

Lodge a booking REQUEST for any fixed-price route — airport or cruise terminal. It is created as pending; the operator confirms and the customer receives a payment link by email. No payment happens through this tool. Confirm all details with the customer first.

SERVERBooking SOURCEhttps://gc-airporttransfers.com/wp-json/atb-gateway/v1/mcp
Low RISK CLASS
Category Read
Parameters 128 required
Recommended Allowedsee the rule below
Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-gc-airporttransfers-booking/request-booking.md

What request_booking does on Booking

AI agents call request_booking 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.

ParameterTypeRequiredDescription
pax integer Yes Passengers 1-11
date string Yes YYYY-MM-DD (at least 1 hour ahead; same-day: phone instead)
name string Yes Customer full name
time string Yes HH:MM 24h
email string Yes Customer email (receives acknowledgement + payment link)
notes string Anything else, e.g. child seats with ages (optional)
phone string Yes Customer phone
flight string Flight number (optional, enables free flight tracking)
pickup string Yes Pick-up place
dropoff string Yes Drop-off place
sandbox boolean true = create a TEST booking that never reaches the operator and sends no emails. For integration testing only.
vehicle string sedan | carnival | maxi (auto-upgraded if too small for pax)

Parameters from the server's own tool schema.

Why request_booking is rated Low

Even though request_booking 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.

Risk signalsHigh parameter count (12 properties)

Questions about request_booking

What does the request_booking tool do? +

Lodge a booking REQUEST for any fixed-price route — airport or cruise terminal. It is created as pending; the operator confirms and the customer receives a payment link by email. No payment happens through this tool. Confirm all details with the customer first. It is categorised as a Read tool in the Booking MCP Server, which means it retrieves data without modifying state.

What parameters does request_booking accept? +

request_booking accepts 12 parameters: pax, date, name, time, email, notes, phone, flight, pickup, dropoff, sandbox, vehicle. Required: pax, date, name, time, email, phone, pickup, dropoff. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on request_booking? +

Register the Booking MCP server in PolicyLayer and add a rule for request_booking: 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.

What risk level is request_booking? +

request_booking is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit request_booking? +

Yes. Add a rate_limit block to the request_booking 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.

How do I block request_booking completely? +

Set action: deny in the PolicyLayer policy for request_booking. 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.

What MCP server provides request_booking? +

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Booking's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.