cable_test

Run a cable/TDR test on CX or AOS-S switch ports (async, polls ~60s).

SERVERHpe Networking SOURCEsecure-ssid/hpe-networking-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hpe-networking-mcp/cable-test.md

WHAT IT DOES

What cable_test does on Hpe Networking

AI agents invoke cable_test to trigger actions in Hpe Networking. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why cable_test is rated High

This tool actively triggers a hardware diagnostic test (TDR/cable test) on physical switch ports. It executes an operation on network infrastructure that sends electrical signals through cables, which could briefly disrupt port operation.

From the tool's definition 'Run a cable/TDR test on CX or AOS-S switch ports (async, polls ~60s)'

Attacks that exploit this kind of access

RECOMMENDED RULE

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

cable_test Rate-limited

cable_test stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cable_test": {
      "limits": [
        {
          "counter": "cable_test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about cable_test

What does the cable_test tool do? +

Run a cable/TDR test on CX or AOS-S switch ports (async, polls ~60s). It is categorised as a Execute tool in the Hpe Networking MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cable_test? +

Register the Hpe Networking MCP server in PolicyLayer and add a rule for cable_test: 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 cable_test? +

cable_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cable_test? +

Yes. Add a rate_limit block to the cable_test 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 cable_test completely? +

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

cable_test 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 → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →