weather.airnow.current_latlng
Current AQI observations near a US coordinate. Same fields as current_zip. EPA AirNow
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/weather.airnow.current-latlng.md
What weather.airnow.current_latlng does on Apibase
AI agents call weather.airnow.current_latlng 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 (decimal degrees, e.g. 40.7128 for NYC). |
lng | number | Yes | Longitude (decimal degrees, e.g. -74.0060 for NYC). |
distance | integer | — | Search radius in miles around the coordinate (default 25). |
Parameters from the server's own tool schema.
Why weather.airnow.current_latlng is rated Low
Retrieves current air quality data without modification, creation, or external side effects.
From the tool's definition Current AQI observations near a US coordinate. Query only.
Attacks that exploit this kind of access
The rule that runs weather.airnow.current_latlng 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 weather.airnow.current_latlng, this is the rule to start with:
weather.airnow.current_latlng 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 weather.airnow.current_latlng call is checked against it from then on.
Questions about weather.airnow.current_latlng
Current AQI observations near a US coordinate. Same fields as current_zip. EPA AirNow. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
weather.airnow.current_latlng accepts 3 parameters: lat, lng, distance. Required: lat, lng. 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 weather.airnow.current_latlng: 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.
weather.airnow.current_latlng 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 weather.airnow.current_latlng 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 weather.airnow.current_latlng. 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.
weather.airnow.current_latlng 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