get_air_quality
A read tool on the Hpe Networking MCP server.
This record as markdown: /tools/hpe-networking-mcp/get-air-quality.md
What get_air_quality does on Hpe Networking
AI agents call get_air_quality to retrieve information from Hpe Networking without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_air_quality is rated Low
This tool retrieves air quality information, consistent with the server's stated purpose of providing 'air quality data.' It performs a read operation with no side effects, modifications, or ability to affect external systems.
From the tool's definition Tool named 'get_air_quality' on a weather MCP server alongside data retrieval tools like 'get_current_weather' and 'get_weather_forecast'.
Attacks that exploit this kind of access
The rule that runs get_air_quality safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hpe Networking, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_air_quality, this is the rule to start with:
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 Hpe Networking, apply this rule, and every get_air_quality call is checked against it from then on.
Questions about get_air_quality
get_air_quality is a read tool on the Hpe Networking MCP server. It is categorised as a Read tool in the Hpe Networking MCP Server, which means it retrieves data without modifying state.
Register the Hpe Networking 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 Hpe Networking. 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 Hpe Networking MCP server (secure-ssid/hpe-networking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hpe Networking, and thousands of servers like it.
This server
Across the catalogue