edgeconnect_get_tunnel_metadata
Get EdgeConnect tunnel count metadata from Orchestrator.
This record as markdown: /tools/hpe-networking-mcp/edgeconnect-get-tunnel-metadata.md
What edgeconnect_get_tunnel_metadata does on Hpe Networking
AI agents call edgeconnect_get_tunnel_metadata 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 edgeconnect_get_tunnel_metadata is rated Low
This tool retrieves tunnel metadata information from the Orchestrator system. The 'get_' action pattern combined with 'metadata' indicates a read-only query operation. There are no indications of data creation, modification, deletion, code execution, or financial operations. The blast radius of misuse is minimal as it only exposes visibility into existing tunnel configurations without ability to alter them.
From the tool's definition Tool name contains 'get_' prefix and description states 'Get EdgeConnect tunnel count metadata', indicating data retrieval operation with no modification or execution side effects.
Attacks that exploit this kind of access
The rule that runs edgeconnect_get_tunnel_metadata 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_get_tunnel_metadata, this is the rule to start with:
edgeconnect_get_tunnel_metadata 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 edgeconnect_get_tunnel_metadata call is checked against it from then on.
Questions about edgeconnect_get_tunnel_metadata
Get EdgeConnect tunnel count metadata from Orchestrator. 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 edgeconnect_get_tunnel_metadata: 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.
edgeconnect_get_tunnel_metadata 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 edgeconnect_get_tunnel_metadata 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 edgeconnect_get_tunnel_metadata. 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.
edgeconnect_get_tunnel_metadata 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