faa_public_aviation_search_runways

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 110 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/faa-public-aviation-search-runways.md

WHAT IT DOES

What faa_public_aviation_search_runways does on Livedatalink

AI agents call faa_public_aviation_search_runways to retrieve information from Livedatalink 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	—	Maximum runways. Default 20.
`state`	string	—	Two-letter U.S. state or territory code.
`offset`	integer	—	Runways to skip. Default 0.
`surface`	string	—	Substring of FAA surface code, such as ASPH, CONC, TURF, WATER, or GRVL.
`ils_only`	boolean	—	Require at least one runway end with a published ILS type. Default false.
`lighted_only`	boolean	—	Require a nonblank FAA runway-light code. Default false.
`min_width_ft`	integer	—	Minimum published runway width in feet; water landing areas may be much wider than paved runways.
`min_length_ft`	integer	—	Minimum published runway length in feet.
`public_use_only`	boolean	—	Require FAA public-use classification. Default false.
`response_format`	string	—	Human-readable markdown or machine-readable JSON. Default markdown.
`operational_only`	boolean	—	Exclude closed facilities. Default true.

Parameters from the server's own tool schema.

RISK

Why faa_public_aviation_search_runways is rated Low

Even though faa_public_aviation_search_runways 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.

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs faa_public_aviation_search_runways safely

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

faa_public_aviation_search_runways Allowed

faa_public_aviation_search_runways 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": {
    "faa_public_aviation_search_runways": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every faa_public_aviation_search_runways call is checked against it from then on.

FAQ

Questions about faa_public_aviation_search_runways

What does the faa_public_aviation_search_runways tool do? +

Search U.S. FAA NASR runways using bounded technical filters such as state, minimum published length/width, surface text, lighting, ILS, public use, and operational status. Returns the airport identity, runway dimensions/surface/condition/lighting, weight fields, ILS/approach-light end counts, pagination, cycle, and provenance. Use this for 'operational Texas runways at least 8,000 feet', 'public-use paved runways in Alaska', or airport-site screening. Reference data only; verify all performance and operational decisions independently. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does faa_public_aviation_search_runways accept? +

faa_public_aviation_search_runways accepts 11 parameters: limit, state, offset, surface, ils_only, lighted_only, min_width_ft, min_length_ft, public_use_only, response_format, operational_only. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on faa_public_aviation_search_runways? +

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

What risk level is faa_public_aviation_search_runways? +

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

Can I rate-limit faa_public_aviation_search_runways? +

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

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

faa_public_aviation_search_runways is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 381 Livedatalink tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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