Low Risk

get_itinerary_details

Get detailed information about a specific flight itinerary. Returns comprehensive details including: - Complete flight segments with airline, flight number, times, and aircraft type - Departure and arrival terminals (if available) - Baggage allowance (checked bags, carry-on, personal item limits)...

Part of the World Airfares Flight Search server.

get_itinerary_details is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE WORLD AIRFARES FLIGHT SEARCH →

Free to start. No card required.

AI agents call get_itinerary_details to retrieve information from World Airfares Flight Search without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_itinerary_details only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_itinerary_details": {}
  }
}

See the full World Airfares Flight Search policy for all 3 tools.

Get this rule live on your own World Airfares Flight Search server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY WORLD AIRFARES FLIGHT SEARCH →

These attack patterns abuse exactly the kind of access get_itinerary_details gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_itinerary_details only ever does what you allow.

SECURE WORLD AIRFARES FLIGHT SEARCH →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_itinerary_details tool do? +

Get detailed information about a specific flight itinerary. Returns comprehensive details including: - Complete flight segments with airline, flight number, times, and aircraft type - Departure and arrival terminals (if available) - Baggage allowance (checked bags, carry-on, personal item limits) - Layover information (duration, airport, overnight status) - Fare rules (refundability, change policy, fees) - Price breakdown (base fare, taxes, fees) - Booking URL for purchase Use this when user asks for: - 'Tell me more about this flight' - 'What are the baggage allowances?' - 'Is this flight refundable?' - 'Show me the layover details' - 'What terminals will I use?' WIDGET NOTE: If this tool's results are displayed in a visual widget alongside your response, do NOT repeat the itinerary details in text format. Instead, briefly confirm the details are shown. Do NOT prompt users with instructions like 'say show details for RefNo X' — the widget already displays the details interactively. Only use the formatting instructions below when NO visual widget is rendering the results. PRESENTATION FORMATTING (MANDATORY): - Present detailed information in well-formatted sections. Group by flight leg, segment, and then rules/baggage. - CRITICAL: ALWAYS display full names with codes for better readability: * Airports: Use format 'City Name (CODE)' - Example: 'Colombo (CMB)', 'London Heathrow (LHR)', 'Dubai (DXB)' * Airlines: Use format 'Airline Name (CODE)' - Example: 'Emirates (EK)', 'British Airways (BA)', 'Flydubai (FZ)' * NEVER display codes alone (CMB, DXB, EK, etc.) - users don't recognize them * ALWAYS include both the full name and code in parentheses. It is categorised as a Read tool in the World Airfares Flight Search MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_itinerary_details? +

Register the World Airfares Flight Search MCP server in PolicyLayer and add a rule for get_itinerary_details: 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 World Airfares Flight Search. Nothing to install.

What risk level is get_itinerary_details? +

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

Can I rate-limit get_itinerary_details? +

Yes. Add a rate_limit block to the get_itinerary_details 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 get_itinerary_details completely? +

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

get_itinerary_details is provided by the World Airfares Flight Search MCP server (https://mcp.worldairfares.com). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every World Airfares Flight Search tool call.

Deterministic rules across all 3 World Airfares Flight Search tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.