edgeconnect_list_tunnels

List EdgeConnect physical tunnels with compact health/status fields.

SERVERHpe Networking SOURCEsecure-ssid/hpe-networking-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hpe-networking-mcp/edgeconnect-list-tunnels.md

WHAT IT DOES

What edgeconnect_list_tunnels does on Hpe Networking

AI agents call edgeconnect_list_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.

RISK

Why edgeconnect_list_tunnels is rated Low

The verb 'list' combined with the description focusing on retrieving tunnel status and health data confirms this is a read operation with no side effects. It queries existing network tunnel state without creating, modifying, or deleting resources. Blast radius is minimal—an agent cannot cause harm by listing tunnels.

From the tool's definition Tool name 'edgeconnect_list_tunnels' and description 'List EdgeConnect physical tunnels with compact health/status fields' indicate a read-only query operation that retrieves tunnel information without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs edgeconnect_list_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 edgeconnect_list_tunnels, this is the rule to start with:

edgeconnect_list_tunnels Allowed

edgeconnect_list_tunnels is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "edgeconnect_list_tunnels": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hpe Networking, apply this rule, and every edgeconnect_list_tunnels call is checked against it from then on.

FAQ

Questions about edgeconnect_list_tunnels

What does the edgeconnect_list_tunnels tool do? +

List EdgeConnect physical tunnels with compact health/status fields. It is categorised as a Read tool in the Hpe Networking MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on edgeconnect_list_tunnels? +

Register the Hpe Networking MCP server in PolicyLayer and add a rule for edgeconnect_list_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.

What risk level is edgeconnect_list_tunnels? +

edgeconnect_list_tunnels is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit edgeconnect_list_tunnels? +

Yes. Add a rate_limit block to the edgeconnect_list_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.

How do I block edgeconnect_list_tunnels completely? +

Set action: deny in the PolicyLayer policy for edgeconnect_list_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.

What MCP server provides edgeconnect_list_tunnels? +

edgeconnect_list_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.

KEEP EXPLORING

More on Hpe Networking, and thousands of servers like it.

This server

All 595 Hpe Networking tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →