openmeteoaq.air.historical
Retrieve hourly historical air quality data for a date range at any global location. Returns PM10, PM2.5, ozone, nitrogen dioxide, European AQI, US AQI and other pollutants. Historical data available from 2022-01-01. Maximum query range ~1 year per call. Copernicus CAMS reanalysis, no auth. Open-...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/openmeteoaq.air.historical.md
What openmeteoaq.air.historical does on Apibase
AI agents call openmeteoaq.air.historical 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 |
|---|---|---|---|
end_date | string | Yes | End date in YYYY-MM-DD format (e.g. "2024-01-31"). Maximum range is ~1 year per query. |
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) |
pollutants | string | — | Comma-separated pollutant variables to return. Available: pm10, pm2_5, carbon_monoxide, nitrogen_dioxide, sulphur_dioxide, ozone, aerosol_optical_depth, dust, u |
start_date | string | Yes | Start date in YYYY-MM-DD format (e.g. "2024-01-01"). Historical data from 2022. |
Parameters from the server's own tool schema.
Why openmeteoaq.air.historical is rated Low
Tool retrieves historical air quality data with no side effects, modifications, or destructive operations.
From the tool's definition Retrieve hourly historical air quality data for a date range at any global location.
Attacks that exploit this kind of access
The rule that runs openmeteoaq.air.historical 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.historical, this is the rule to start with:
openmeteoaq.air.historical 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.historical call is checked against it from then on.
Questions about openmeteoaq.air.historical
Retrieve hourly historical air quality data for a date range at any global location. Returns PM10, PM2.5, ozone, nitrogen dioxide, European AQI, US AQI and other pollutants. Historical data available from 2022-01-01. Maximum query range ~1 year per call. Copernicus CAMS reanalysis, no auth. 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.historical accepts 6 parameters: end_date, latitude, timezone, longitude, pollutants, start_date. Required: end_date, latitude, longitude, start_date. 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.historical: 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.historical 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.historical 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.historical. 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.historical 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