openmeteoaq.air.current
Get real-time air quality conditions for any global location using Copernicus CAMS data. Returns PM10, PM2.5 (μg/m³), carbon monoxide, nitrogen dioxide, sulphur dioxide, ozone, aerosol optical depth, dust, UV index, ammonia, European AQI (0–500 CAQI scale), and US AQI (0–500+ EPA scale). No API k...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/openmeteoaq.air.current.md
What openmeteoaq.air.current does on Apibase
AI agents call openmeteoaq.air.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 |
|---|---|---|---|
latitude | number | Yes | Latitude of the location in decimal degrees (e.g. 48.8566 for Paris) |
timezone | string | — | IANA timezone name for returned timestamps (e.g. "Europe/Paris", "America/New_York"). Defaults to UTC. |
longitude | number | Yes | Longitude of the location in decimal degrees (e.g. 2.3522 for Paris) |
Parameters from the server's own tool schema.
Why openmeteoaq.air.current is rated Low
Read-only retrieval of air quality data with no side effects.
From the tool's definition Get real-time air quality conditions for any global location
Attacks that exploit this kind of access
The rule that runs openmeteoaq.air.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 openmeteoaq.air.current, this is the rule to start with:
openmeteoaq.air.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 openmeteoaq.air.current call is checked against it from then on.
Questions about openmeteoaq.air.current
Get real-time air quality conditions for any global location using Copernicus CAMS data. Returns PM10, PM2.5 (μg/m³), carbon monoxide, nitrogen dioxide, sulphur dioxide, ozone, aerosol optical depth, dust, UV index, ammonia, European AQI (0–500 CAQI scale), and US AQI (0–500+ EPA scale). No API key required. Coverage: global, hourly updates. Open-source Open-Meteo — CC BY 4.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
openmeteoaq.air.current accepts 3 parameters: latitude, timezone, longitude. Required: latitude, longitude. 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 openmeteoaq.air.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.
openmeteoaq.air.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 openmeteoaq.air.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 openmeteoaq.air.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.
openmeteoaq.air.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