diagnose_connectivity · Netmiko MCP Server MCP

WHAT IT DOES

What diagnose_connectivity does on Netmiko MCP Server

AI agents invoke diagnose_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 diagnose_connectivity needs a policy

This tool executes diagnostic operations against live network devices over SSH using Netmiko. While the primary intent is read/analysis, 'suggests fixes' and 'comprehensive diagnostics' implies it may run active tests (ping, traceroute, debug commands) and potentially apply changes.

From the tool's definition 'Performs comprehensive diagnostics and suggests fixes' - actively runs diagnostic operations on network devices via SSH; 'AI-powered' troubleshooting implies automated execution of multiple commands

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

diagnose_connectivity Rate-limited

diagnose_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": {
    "diagnose_connectivity": {
      "limits": [
        {
          "counter": "diagnose_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 diagnose_connectivity

What does the diagnose_connectivity tool do? +

AI-powered connectivity troubleshooting. Performs comprehensive diagnostics and suggests fixes. 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 diagnose_connectivity? +

Register the Netmiko MCP Server MCP server in PolicyLayer and add a rule for diagnose_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 diagnose_connectivity? +

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

Can I rate-limit diagnose_connectivity? +

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

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

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