check_network_connectivity · Mcp Ssh MCP: Risk & Policy

WHAT IT DOES

What check_network_connectivity does on Mcp Ssh

AI agents invoke check_network_connectivity to trigger actions in Mcp Ssh. 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 check_network_connectivity needs a policy

This tool actively triggers network tests (e.g., ping, traceroute, curl) from the remote server, which constitutes executing operations on a remote system. While primarily diagnostic/read-like in intent, it runs active network probes that generate outbound traffic from the server. Misuse could be used to probe internal networks or exfiltrate data covertly, giving it medium severity.

From the tool's definition Test outbound network connectivity from the remote server

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

check_network_connectivity Rate-limited

check_network_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": {
    "check_network_connectivity": {
      "limits": [
        {
          "counter": "check_network_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 Mcp Ssh, so you can run agents against it safely.

FAQ

Questions about check_network_connectivity

What does the check_network_connectivity tool do? +

Test outbound network connectivity from the remote server. It is categorised as a Execute tool in the Mcp Ssh MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on check_network_connectivity? +

Register the Mcp Ssh MCP server in PolicyLayer and add a rule for check_network_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 Mcp Ssh. Nothing to install.

What risk level is check_network_connectivity? +

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

Can I rate-limit check_network_connectivity? +

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

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

check_network_connectivity is provided by the Mcp Ssh MCP server (zhouxiangjing/mcp-ssh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.