Get air quality forecast data including PM2.5, PM10, ozone, nitrogen dioxide and other pollutants.
AI agents call air_quality to retrieve information from Open Meteo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves air quality forecast information (PM2.5, PM10, ozone, nitrogen dioxide, etc.) from the Open-Meteo API. It has no side effects, does not modify data, execute code, delete records, or move money. It is purely a read operation that returns environmental sensor data and forecasts.
From the tool's definition Tool description states 'Get air quality forecast data' — a retrieval operation with no modification, deletion, or execution of external processes. Returns weather/environmental data only.
Attacks that exploit this kind of access
Get air quality forecast data including PM2.5, PM10, ozone, nitrogen dioxide and other pollutants. It is categorised as a Read tool in the Open Meteo MCP Server, which means it retrieves data without modifying state.
Register the Open Meteo MCP server in PolicyLayer and add a rule for air_quality: 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 Open Meteo. Nothing to install.
air_quality 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 air_quality 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 air_quality. 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.
air_quality is provided by the Open Meteo MCP server (windsornguyen/open-meteo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →