get_air_quality
AI agents call get_air_quality to retrieve information from MCP-server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates a retrieval operation with no side effects. It fits the pattern of the weather-related Read tools on this server (all prefixed with 'get_'). However, confidence is moderately reduced (0.7 rather than 0.9+) because the description is empty, leaving some ambiguity about the actual implementation and whether it might have unexpected side effects.
From the tool's definition Tool name 'get_air_quality' strongly suggests a read-only query operation that retrieves air quality data, consistent with sibling weather tools (get_current_weather, get_historical_weather, get_weather_alerts, get_weather_forecast) which are all Read…
Attacks that exploit this kind of access
get_air_quality. It is categorised as a Read tool in the MCP-server MCP Server, which means it retrieves data without modifying state.
Register the 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 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 MCP-server MCP server (prathapmahi/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 →