aviation.metar.current
Current METAR (METeorological Aerodrome Report) for one or more airports — official aviation weather observations (wind, visibility, sky condition, temperature, dewpoint, altimeter, remarks). Updates every 1 hour, more often when conditions change rapidly.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/aviation.metar.current.md
What aviation.metar.current does on Apibase
AI agents call aviation.metar.current 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 |
|---|---|---|---|
hours | integer | — | Hours of history to return (default 2, max 72) |
icao_codes | string | Yes | Comma-separated ICAO airport codes (uppercase, 4 letters each, e.g. 'KJFK,KLAX,EGLL,RJTT'). Max 20 per call. Examples: KJFK (New York JFK), EGLL (London Heathro |
Parameters from the server's own tool schema.
Why aviation.metar.current is rated Low
Retrieves read-only weather data; no mutations, no execution, no financial impact.
From the tool's definition Current METAR... official aviation weather observations
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs aviation.metar.current 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 aviation.metar.current, this is the rule to start with:
aviation.metar.current 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 aviation.metar.current call is checked against it from then on.
Questions about aviation.metar.current
Current METAR (METeorological Aerodrome Report) for one or more airports — official aviation weather observations (wind, visibility, sky condition, temperature, dewpoint, altimeter, remarks). Updates every 1 hour, more often when conditions change rapidly. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
aviation.metar.current accepts 2 parameters: hours, icao_codes. Required: icao_codes. 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 aviation.metar.current: 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.
aviation.metar.current 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 aviation.metar.current 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 aviation.metar.current. 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.
aviation.metar.current 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