4 tools. 1 can modify or destroy data without limits.
1 destructive tool with no built-in limits. Policy required.
Last updated:
Community server · catalogue entry verified 12/06/2026
Running more than one server? Check your whole stack →
1 of Flights MCP's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and Flights MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"request_booking_link": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
} Financial tools should be explicitly enabled per use case, not open by default.
{
"get_flight_option_details": {
"limits": [
{
"counter": "get_flight_option_details_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Free to start. No card required.
Yes. The Flights MCP server exposes 1 financial tools including request_booking_link. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.
4 tools across 1 categories: Read. 3 are read-only. 1 can modify, create, or delete data.
Register the Flights MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 4 Flights MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Flights MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.