environment.airquality.nearest
Real-time air quality index (AQI) and weather data for the nearest monitoring station to given GPS coordinates. Returns nearest city, AQI (US + CN), dominant pollutant, PM2.5/PM10/O3 concentrations, temperature, humidity (IQAir AirVisual)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/environment.airquality.nearest.md
What environment.airquality.nearest does on Apibase
AI agents call environment.airquality.nearest 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 |
|---|---|---|---|
lat | number | Yes | Latitude (-90 to 90, e.g. 34.0522) |
lon | number | Yes | Longitude (-180 to 180, e.g. -118.2437) |
Parameters from the server's own tool schema.
Why environment.airquality.nearest is rated Low
Retrieves environmental monitoring data without side effects or modifications to systems.
From the tool's definition Real-time air quality index, weather data, Returns nearest city, AQI, pollutant
Attacks that exploit this kind of access
The rule that runs environment.airquality.nearest 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 environment.airquality.nearest, this is the rule to start with:
environment.airquality.nearest 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 environment.airquality.nearest call is checked against it from then on.
Questions about environment.airquality.nearest
Real-time air quality index (AQI) and weather data for the nearest monitoring station to given GPS coordinates. Returns nearest city, AQI (US + CN), dominant pollutant, PM2.5/PM10/O3 concentrations, temperature, humidity (IQAir AirVisual). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
environment.airquality.nearest accepts 2 parameters: lat, lon. Required: lat, lon. 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 environment.airquality.nearest: 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.
environment.airquality.nearest 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 environment.airquality.nearest 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 environment.airquality.nearest. 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.
environment.airquality.nearest 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