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

aviationweather.reference.stations

Look up aviation weather observation stations by ICAO identifier(s), bounding box, or US state. Returns station metadata: ICAO, IATA, FAA, and WMO identifiers; site name; coordinates; elevation; country/state; and observation types supported (METAR, TAF, PIREP). Useful for discovering station ide...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 30 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/aviationweather.reference.stations.md

What aviationweather.reference.stations does on Apibase

AI agents call aviationweather.reference.stations 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.

ParameterTypeRequiredDescription
ids string — Comma-separated ICAO station identifiers to look up (e.g. "KJFK,KLAX"). Use this OR bbox OR state — not together.
bbox string — Bounding box in decimal degrees: "minLat,minLon,maxLat,maxLon" (e.g. "25,-125,50,-65" for the contiguous US). Returns all aviation weather stations within the b
state string — Two-letter US state abbreviation to filter stations by state (e.g. "TX", "CA"). Returns all aviation weather stations in that state.

Parameters from the server's own tool schema.

Why aviationweather.reference.stations is rated Low

Queries public aviation weather station data with no side effects or modifications.

From the tool's definition Look up aviation weather observation stations, returns station metadata

Questions about aviationweather.reference.stations

What does the aviationweather.reference.stations tool do? +

Look up aviation weather observation stations by ICAO identifier(s), bounding box, or US state. Returns station metadata: ICAO, IATA, FAA, and WMO identifiers; site name; coordinates; elevation; country/state; and observation types supported (METAR, TAF, PIREP). Useful for discovering station identifiers before calling METAR or TAF tools. Provide one of: ids (comma-separated ICAO codes), bbox (minLat,minLon,maxLat,maxLon), or state (2-letter US). Source: NOAA Aviation Weather Center — US Government public domain, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does aviationweather.reference.stations accept? +

aviationweather.reference.stations accepts 3 parameters: ids, bbox, state. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on aviationweather.reference.stations? +

Register the Apibase MCP server in PolicyLayer and add a rule for aviationweather.reference.stations: 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.

What risk level is aviationweather.reference.stations? +

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

Can I rate-limit aviationweather.reference.stations? +

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

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

aviationweather.reference.stations 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.

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 Apibase'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.