Get air pollution data for a city.
AI agents call get_air_pollution to retrieve information from OpenWeatherMap MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves air quality/pollution information from the OpenWeatherMap API without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk—exposure would only allow unauthorized querying of publicly available weather/air quality data.
From the tool's definition Tool name 'get_air_pollution' and description 'Get air pollution data for a city' indicate pure data retrieval with no modification, deletion, or execution of external operations. The verb 'Get' is passive and retrieval-focused.
Attacks that exploit this kind of access
Get air pollution data for a city. It is categorised as a Read tool in the OpenWeatherMap MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenWeatherMap MCP Server MCP server in PolicyLayer and add a rule for get_air_pollution: 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 OpenWeatherMap MCP Server. Nothing to install.
get_air_pollution 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 get_air_pollution 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 get_air_pollution. 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.
get_air_pollution is provided by the OpenWeatherMap MCP Server MCP server (mattiaperi/openweathermap-mcp-server). 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 →