ssh

A execute tool on the GNS3 MCP server.

SERVERGNS3 MCP Server SOURCEchistokhinsv/gns3-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/chistokhinsv-gns3-mcp/ssh.md

WHAT IT DOES

What ssh does on GNS3 MCP Server

AI agents invoke ssh to trigger actions in GNS3 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.

RISK

Why ssh is rated High

SSH tools run remote commands on target systems. In the context of GNS3 network automation, SSH access to nodes likely enables arbitrary command execution on virtual network devices. The description is empty, reducing confidence, but the server context and tool name strongly imply remote command execution capability.

From the tool's definition Tool name 'ssh' on a GNS3 server described as enabling control of network lab automation including 'consoles, and SSH'. SSH tools typically execute remote shell commands on network devices.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ssh safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GNS3 MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ssh, this is the rule to start with:

ssh Rate-limited

ssh 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": {
    "ssh": {
      "limits": [
        {
          "counter": "ssh_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 GNS3 MCP Server, apply this rule, and every ssh call is checked against it from then on.

FAQ

Questions about ssh

What does the ssh tool do? +

ssh is a execute tool on the GNS3 MCP Server MCP server. It is categorised as a Execute tool in the GNS3 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 ssh? +

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

What risk level is ssh? +

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

Can I rate-limit ssh? +

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

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

ssh is provided by the GNS3 MCP Server MCP server (chistokhinsv/gns3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GNS3 MCP Server, and thousands of servers like it.

This server

All 16 GNS3 MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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