avwx.stations.summary

Composite report for one airport — latest parsed METAR + TAF + station info (name, lat/lon/elev, type) in one call. Cheaper than three separate calls if you need the full picture.

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/avwx.stations.summary.md

WHAT IT DOES

What avwx.stations.summary does on Apibase

AI agents call avwx.stations.summary 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 code (4-letter uppercase). Examples: KJFK, EGLL, KSFO.

Parameters from the server's own tool schema.

RISK

Why avwx.stations.summary is rated Low

Fetches aviation weather data and airport metadata; read-only operation with no modifications or external triggers.

From the tool's definition retrieves latest parsed METAR + TAF + station info; no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs avwx.stations.summary 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.stations.summary, this is the rule to start with:

avwx.stations.summary Allowed

avwx.stations.summary is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "avwx.stations.summary": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every avwx.stations.summary call is checked against it from then on.

FAQ

Questions about avwx.stations.summary

What does the avwx.stations.summary tool do? +

Composite report for one airport — latest parsed METAR + TAF + station info (name, lat/lon/elev, type) in one call. Cheaper than three separate calls if you need the full picture. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does avwx.stations.summary accept? +

avwx.stations.summary accepts 1 parameter: icao_code. Required: icao_code. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on avwx.stations.summary? +

Register the Apibase MCP server in PolicyLayer and add a rule for avwx.stations.summary: 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 avwx.stations.summary? +

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

Can I rate-limit avwx.stations.summary? +

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

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

avwx.stations.summary 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →