weather-get-air-quality
Get air quality data (PM2.5, ozone, dust, etc.) for a specific location.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/weather-get-air-quality.md
What weather-get-air-quality does on Meta Data Mcp
AI agents call weather-get-air-quality to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why weather-get-air-quality is rated Low
This tool queries an open data API to retrieve air quality metrics (PM2.5, ozone, dust) for a location. It is a read-only operation that retrieves public environmental data without side effects. No data is created, modified, deleted, or financial transactions occur. The blast radius of misuse is minimal—an agent could only retrieve environmental data, which is already public.
From the tool's definition Tool name 'weather-get-air-quality' and description 'Get air quality data' indicate retrieval of existing environmental data with no modifications, deletions, or external state changes.
Attacks that exploit this kind of access
The rule that runs weather-get-air-quality safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For weather-get-air-quality, this is the rule to start with:
weather-get-air-quality is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every weather-get-air-quality call is checked against it from then on.
Questions about weather-get-air-quality
Get air quality data (PM2.5, ozone, dust, etc.) for a specific location. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for weather-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 Meta Data Mcp. Nothing to install.
weather-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 weather-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 weather-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.
weather-get-air-quality is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue