Get tunnel health summary (up/down counts) for a gateway cluster.
AI agents call get_cluster_tunnel_health to retrieve information from API-Central without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves monitoring data about gateway cluster tunnel status. It performs no writes, deletions, code execution, or financial operations. The retrieval of health metrics is a read-only operation typical of network monitoring and diagnostics. Low severity reflects that gathering infrastructure status information poses minimal risk even if misused by an agent.
From the tool's definition Tool name is 'get_cluster_tunnel_health' and description states it retrieves 'tunnel health summary (up/down counts)' — uses 'get' verb and describes a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get tunnel health summary (up/down counts) for a gateway cluster. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for get_cluster_tunnel_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 API-Central. Nothing to install.
get_cluster_tunnel_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_cluster_tunnel_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_cluster_tunnel_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_cluster_tunnel_health is provided by the API-Central MCP server (secure-ssid/centralmcp). 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 →