checkwx.stations.info
Airport/weather-station metadata by ICAO — name, IATA, latitude/longitude/elevation, country, city, time zone, runway info (count, longest length, surface).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/checkwx.stations.info.md
What checkwx.stations.info does on Apibase
AI agents call checkwx.stations.info 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 |
|---|---|---|---|
icao_code | string | Yes | Single ICAO airport/station code (4-letter uppercase). Examples: 'KJFK', 'EGLL', 'RJTT'. |
Parameters from the server's own tool schema.
Why checkwx.stations.info is rated Low
Retrieves public airport/weather-station metadata without modifying data or enabling harmful actions.
From the tool's definition metadata by ICAO — name, IATA, latitude/longitude/elevation, country, city, time zone, runway info
Attacks that exploit this kind of access
The rule that runs checkwx.stations.info 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 checkwx.stations.info, this is the rule to start with:
checkwx.stations.info 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 checkwx.stations.info call is checked against it from then on.
Questions about checkwx.stations.info
Airport/weather-station metadata by ICAO — name, IATA, latitude/longitude/elevation, country, city, time zone, runway info (count, longest length, surface). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
checkwx.stations.info accepts 1 parameter: 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 checkwx.stations.info: 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.
checkwx.stations.info 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 checkwx.stations.info 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 checkwx.stations.info. 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.
checkwx.stations.info 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