test_end_to_end_connectivity · Netmiko MCP Server MCP

WHAT IT DOES

What test_end_to_end_connectivity does on Netmiko MCP Server

AI agents invoke test_end_to_end_connectivity to trigger actions in Netmiko MCP Server. 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.

WHY IT NEEDS A POLICY

Why test_end_to_end_connectivity needs a policy

This tool executes ping commands on network devices to test bidirectional connectivity. It triggers external network operations (ICMP ping tests) on Cisco devices via SSH using Netmiko. While it is read-like in intent (testing/monitoring), it actively executes commands on network infrastructure.

From the tool's definition Test full connectivity between two routers (bidirectional ping test)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_end_to_end_connectivity Rate-limited

test_end_to_end_connectivity 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": {
    "test_end_to_end_connectivity": {
      "limits": [
        {
          "counter": "test_end_to_end_connectivity_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Netmiko MCP Server, so you can run agents against it safely.

FAQ

Questions about test_end_to_end_connectivity

What does the test_end_to_end_connectivity tool do? +

Test full connectivity between two routers (bidirectional ping test). It is categorised as a Execute tool in the Netmiko MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_end_to_end_connectivity? +

Register the Netmiko MCP Server MCP server in PolicyLayer and add a rule for test_end_to_end_connectivity: 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 Netmiko MCP Server. Nothing to install.

What risk level is test_end_to_end_connectivity? +

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

Can I rate-limit test_end_to_end_connectivity? +

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

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

test_end_to_end_connectivity is provided by the Netmiko MCP Server MCP server (owen123-lang/netmiko_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.