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

aviationweather.observation.pirep

Retrieve Pilot Reports (PIREPs) near a given ICAO station within a configurable radius and time window. PIREPs are real-time in-flight observations filed by pilots capturing actual icing severity, turbulence intensity, visibility, cloud bases and tops, and conditions at flight level. Returns deco...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 31 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.observation.pirep.md

What aviationweather.observation.pirep does on Apibase

AI agents call aviationweather.observation.pirep 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
id string Yes ICAO station identifier to use as the geographic center of the search (e.g. "KJFK", "KORD"). Pilot reports within `distance` nautical miles of this station and
age integer — How many hours back to search for pilot reports (1–24, default 2).
distance integer — Search radius in nautical miles around the station (10–200, default 100). 100 nm covers the typical terminal area plus en-route corridor.

Parameters from the server's own tool schema.

Why aviationweather.observation.pirep is rated Low

Tool retrieves publicly available aviation weather observations with no side effects or data modification capabilities.

From the tool's definition Retrieve Pilot Reports near given ICAO station within configurable radius

Questions about aviationweather.observation.pirep

What does the aviationweather.observation.pirep tool do? +

Retrieve Pilot Reports (PIREPs) near a given ICAO station within a configurable radius and time window. PIREPs are real-time in-flight observations filed by pilots capturing actual icing severity, turbulence intensity, visibility, cloud bases and tops, and conditions at flight level. Returns decoded fields: flight level, icing and turbulence extents, and raw PIREP text. Useful for pre-flight planning, route analysis, and verifying forecast accuracy. 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.observation.pirep accept? +

aviationweather.observation.pirep accepts 3 parameters: id, age, distance. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on aviationweather.observation.pirep? +

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

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

Can I rate-limit aviationweather.observation.pirep? +

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

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

aviationweather.observation.pirep 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.