flight.route-schedule

Scheduled flights between two airports over a date window (FlightAware AeroAPI). Pass origin and destination (ICAO or IATA) plus startDate/endDate; returns scheduled flights with ident, operator, aircraft type, origin/destination, and scheduled departure/arrival times. Answers \

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/flight.route-schedule.md

WHAT IT DOES

What flight.route-schedule does on Mcp

AI agents call flight.route-schedule to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why flight.route-schedule is rated Low

This tool retrieves flight schedule data from FlightAware AeroAPI. It is a read-only query that returns information about scheduled flights with no side effects. The pay-per-call settlement in USDC is a cost concern but does not constitute a financial transaction initiated by the tool itself on behalf of the user.

From the tool's definition 'Scheduled flights between two airports over a date window'; 'returns scheduled flights with ident, operator, aircraft type, origin/destination, and scheduled departure/arrival times'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs flight.route-schedule safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For flight.route-schedule, this is the rule to start with:

flight.route-schedule Allowed

flight.route-schedule is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "flight.route-schedule": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every flight.route-schedule call is checked against it from then on.

FAQ

Questions about flight.route-schedule

What does the flight.route-schedule tool do? +

How do I enforce a policy on flight.route-schedule? +

Register the MCP server in PolicyLayer and add a rule for flight.route-schedule: 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 Mcp. Nothing to install.

What risk level is flight.route-schedule? +

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

Can I rate-limit flight.route-schedule? +

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

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

flight.route-schedule is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

aiva_get_delivery_schedule on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →