get_cluster_tunnels
List tunnels for a gateway cluster.
This record as markdown: /tools/hpe-networking-mcp/get-cluster-tunnels.md
What get_cluster_tunnels does on Hpe Networking
AI agents call get_cluster_tunnels 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_cluster_tunnels is rated Low
This tool retrieves and lists configuration data about tunnels in a gateway cluster. It performs a read-only query operation with no side effects, no data modification, and no execution of network commands. The blast radius of misuse is limited to information disclosure, which is low severity in a network monitoring context.
From the tool's definition Tool name 'get_cluster_tunnels' uses 'get' verb; description states 'List tunnels' which is a retrieval/query operation with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs get_cluster_tunnels 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_cluster_tunnels, this is the rule to start with:
get_cluster_tunnels 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_cluster_tunnels call is checked against it from then on.
Questions about get_cluster_tunnels
List tunnels for a gateway cluster. 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_cluster_tunnels: 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_cluster_tunnels 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_tunnels 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_tunnels. 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_tunnels 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