get_reporting_service_health
Fetch reporting-service health status from network-reporting/v1alpha1/reports/health.
This record as markdown: /tools/hpe-networking-mcp/get-reporting-service-health.md
What get_reporting_service_health does on Hpe Networking
AI agents call get_reporting_service_health 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_reporting_service_health is rated Low
This tool retrieves health status data from a reporting service endpoint. It performs a read-only query with no side effects, no data modification, and no execution of commands. The low severity reflects minimal blast radius—health status information is non-sensitive operational metadata that cannot be misused to cause harm even if accessed by a compromised agent.
From the tool's definition Tool name includes 'get_' prefix and description uses 'Fetch', indicating data retrieval with no modification. Endpoint is /reports/health which returns status information.
Attacks that exploit this kind of access
The rule that runs get_reporting_service_health 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_reporting_service_health, this is the rule to start with:
get_reporting_service_health 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_reporting_service_health call is checked against it from then on.
Questions about get_reporting_service_health
Fetch reporting-service health status from network-reporting/v1alpha1/reports/health. 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_reporting_service_health: 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_reporting_service_health 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_reporting_service_health 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_reporting_service_health. 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_reporting_service_health 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