Get air quality/pollution data for a location.
AI agents call get_air_quality 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 atmospheric pollution and air quality information for a specified location. It performs a query operation that returns data without modifying, executing, deleting, or creating any resources. The operation is read-only and has no financial implications or destructive potential. Even if misused by an AI agent, it can only fetch publicly available environmental data, presenting minimal risk.
From the tool's definition Tool name 'get_air_quality' and description 'Get air quality/pollution data for a location' indicate data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get_air_quality gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenWeatherMap MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_air_quality:
{
"version": "1",
"default": "deny",
"tools": {
"get_air_quality": {}
}
}get_air_quality is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get air quality/pollution data for a location. 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_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 OpenWeatherMap MCP Server. Nothing to install.
get_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 get_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 get_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.
get_air_quality is provided by the OpenWeatherMap MCP Server MCP server (jezweb/weather-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenWeatherMap MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 OpenWeatherMap MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.