avwx.notams.list
Active NOTAMs (Notice to Airmen) for one or more airports, parsed into structured fields — NOTAM ID, classification (FDC/D/U), type (runway closure, navaid out, airspace restriction, obstacle), effective period, summary text. Critical for flight planning. UNIQUE to AVWX — NOAA and CheckWX do NOT ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/avwx.notams.list.md
What avwx.notams.list does on Apibase
AI agents call avwx.notams.list to retrieve information from Apibase 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 |
|---|---|---|---|
distance | integer | — | Include NOTAMs within this nautical-mile radius (0-100, default 10). Use 0 for airport-specific only. |
icao_code | string | Yes | Single ICAO airport code (4-letter uppercase). Examples: KJFK, EGLL, RJTT, OMDB. |
Parameters from the server's own tool schema.
Why avwx.notams.list is rated Low
Retrieves and parses NOTAM data for airports with no side effects or modifications.
From the tool's definition Active NOTAMs, parsed into structured fields, flight planning
Attacks that exploit this kind of access
The rule that runs avwx.notams.list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For avwx.notams.list, this is the rule to start with:
avwx.notams.list 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 Apibase, apply this rule, and every avwx.notams.list call is checked against it from then on.
Questions about avwx.notams.list
Active NOTAMs (Notice to Airmen) for one or more airports, parsed into structured fields — NOTAM ID, classification (FDC/D/U), type (runway closure, navaid out, airspace restriction, obstacle), effective period, summary text. Critical for flight planning. UNIQUE to AVWX — NOAA and CheckWX do NOT return parsed NOTAMs. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
avwx.notams.list accepts 2 parameters: distance, icao_code. Required: icao_code. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for avwx.notams.list: 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 Apibase. Nothing to install.
avwx.notams.list 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 avwx.notams.list 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 avwx.notams.list. 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.
avwx.notams.list is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue