Get air quality index and pollution data
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.
The tool retrieves and queries air quality data with no side effects, capability to modify data, or execute external operations. It falls squarely within the Read category. Severity is low because misuse would at worst return inaccurate environmental data to an end user, with no destructive, financial, or operational impact.
From the tool's definition Tool name is 'get-air-pollution' with description 'Get air quality index and pollution data'. This is a retrieval operation that queries air quality information without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get air quality index and pollution data. 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 (robertn702/mcp-openweathermap). 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 →