Retrieve detailed information about a specific flight option from the search results.
AI agents call get_flight_option_details to retrieve information from Flights MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays flight details from existing search results. It performs a read-only operation with no ability to modify bookings, execute transactions, or trigger external state changes. The blast radius of misuse is minimal—an agent could retrieve flight information it shouldn't have access to, but cannot book flights, modify existing reservations, or cause financial harm.
From the tool's definition Tool name 'get_flight_option_details' and description 'Retrieve detailed information about a specific flight option from the search results' indicate a query/retrieval operation with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access get_flight_option_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Flights MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_flight_option_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_flight_option_details": {}
}
}get_flight_option_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve detailed information about a specific flight option from the search results. It is categorised as a Read tool in the Flights MCP MCP Server, which means it retrieves data without modifying state.
Register the Flights MCP server in PolicyLayer and add a rule for get_flight_option_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 Flights MCP. Nothing to install.
get_flight_option_details 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 get_flight_option_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.
Set action: deny in the PolicyLayer policy for get_flight_option_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.
get_flight_option_details is provided by the Flights MCP server (maratsarbasov/flights-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Flights MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Flights MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.