find_meetup
Best meet-up airports for travellers from multiple origins, ranked by combined travel effort using the same scoring as the site. Origins can be weighted by traveller count. Scores are kilometre values, lower is better; optimize "score" and "total_distance" both rank by weighted total distance (th...
This record as markdown: /tools/com-flywhereto-mcp/find-meetup.md
What find_meetup does on Fly Where To?
AI agents call find_meetup to retrieve information from Fly Where To? 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 |
|---|---|---|---|
limit | integer | — | Candidates to return (default 5) |
origins | array | Yes | Where the travellers start; duplicates merge by summing travellers |
optimize | string | — | Ranking objective (default "score") |
max_stops | integer | — | Maximum stops per journey (default 0, nonstop only) |
allow_at_home | boolean | — | Allow an origin airport as the meet-up point, that party stays home |
exclude_kinds | array | — | Drop legs whose service kind is in this list, e.g. ["suspended"] |
same_alliance | boolean | — | Require each journey to be flyable within one single airline alliance |
Parameters from the server's own tool schema.
Why find_meetup is rated Low
Even though find_meetup 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 find_meetup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fly Where To?, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_meetup, this is the rule to start with:
find_meetup 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 Fly Where To?, apply this rule, and every find_meetup call is checked against it from then on.
Questions about find_meetup
Best meet-up airports for travellers from multiple origins, ranked by combined travel effort using the same scoring as the site. Origins can be weighted by traveller count. Scores are kilometre values, lower is better; optimize "score" and "total_distance" both rank by weighted total distance (the frontend default), "worst_case" by the longest single journey. Candidates everyone can reach always rank above candidates someone cannot. Route data only: no fares, no frequency or days-of-week data; non-scheduled legs are flagged with a kind field. The map link stores the query as an anonymous share code and reopens it in the site’s meet-up planner. It is categorised as a Read tool in the Fly Where To? MCP Server, which means it retrieves data without modifying state.
find_meetup accepts 7 parameters: limit, origins, optimize, max_stops, allow_at_home, exclude_kinds, same_alliance. Required: origins. The full parameter table on this page comes from the server's own tool schema.
Register the Fly Where To? MCP server in PolicyLayer and add a rule for find_meetup: 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 Fly Where To?. Nothing to install.
find_meetup 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 find_meetup 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 find_meetup. 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.
find_meetup is provided by the Fly Where To? MCP server (https://flywhereto.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fly Where To?, and thousands of servers like it.
This server
Across the catalogue