New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

faa_public_aviation_airport_profile

Return one official FAA NASR facility profile with privacy-minimized airport, runway, and runway-end technical fields. Includes identifiers, coordinates/elevation, status/use, tower and FAR 139 codes, fuel codes, runway length/width/surface/condition/lights, ILS and approach-light fields, declare...

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 21 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-airport-profile.md

What faa_public_aviation_airport_profile does on Livedatalink

AI agents call faa_public_aviation_airport_profile 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.

ParameterTypeRequiredDescription
airport string Yes Exact FAA location id, ICAO id, NASR site number, or unambiguous facility name.
response_format string — Human-readable markdown or machine-readable JSON. Default markdown.

Parameters from the server's own tool schema.

Why faa_public_aviation_airport_profile is rated Low

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

Questions about faa_public_aviation_airport_profile

What does the faa_public_aviation_airport_profile tool do? +

Return one official FAA NASR facility profile with privacy-minimized airport, runway, and runway-end technical fields. Includes identifiers, coordinates/elevation, status/use, tower and FAR 139 codes, fuel codes, runway length/width/surface/condition/lights, ILS and approach-light fields, declared distances, exact cycle, and provenance. Use this for 'FAA profile for JFK', 'runways and approach equipment at KDEN', or technical airport due diligence. It excludes contacts and remarks and is not a substitute for current NOTAMs, charts, or flight planning. 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_airport_profile accept? +

faa_public_aviation_airport_profile accepts 2 parameters: airport, response_format. Required: airport. 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_airport_profile? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for faa_public_aviation_airport_profile: 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_airport_profile? +

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

Can I rate-limit faa_public_aviation_airport_profile? +

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

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

faa_public_aviation_airport_profile 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.

More on Livedatalink, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livedatalink's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.