gns3_stop_all_nodes · GNS3 Network Simulator MCP Server MCP

WHAT IT DOES

What gns3_stop_all_nodes does on GNS3 Network Simulator MCP Server

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

THE RISK

High Risk

Why gns3_stop_all_nodes needs a policy

Stopping all nodes in a GNS3 simulation is an Execute action: it triggers immediate changes to the state of running network devices/simulations. It is not Read (no data retrieval), not Write (not creating/modifying persistent data reversibly), not Destructive (nodes are stopped, not deleted—they can be restarted), and not Financial.

From the tool's definition Tool description states 'Stop all nodes in a project' - directly triggers an action to halt running simulation components. This is an external operation with effects that depend on the project context argument.

Documented attack patterns abuse exactly the kind of access gns3_stop_all_nodes gives an agent:

POLICY

How to control gns3_stop_all_nodes

PolicyLayer is an MCP gateway — it sits between your AI agents and GNS3 Network Simulator MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gns3_stop_all_nodes:

policy.json

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

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

Create a free account and register GNS3 Network Simulator MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GNS3 Network Simulator MCP Server tools

Destructive gns3_delete_link Delete a link between nodes. Destructive gns3_delete_node Delete a node from the project. Destructive gns3_delete_project Permanently delete a project and all its files. Destructive gns3_delete_snapshot Delete a snapshot permanently. Destructive gns3_restore_snapshot Restore a project from a snapshot. Execute gns3_reload_node Reload a node (restart without stopping). Execute gns3_start_all_nodes Start all nodes in a project. Execute gns3_start_capture Start packet capture on a link.

All 42 GNS3 Network Simulator MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in GNS3 Network Simulator MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about gns3_stop_all_nodes

What does the gns3_stop_all_nodes tool do? +

Stop all nodes in a project. It is categorised as a Execute tool in the GNS3 Network Simulator 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 gns3_stop_all_nodes? +

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

What risk level is gns3_stop_all_nodes? +

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

Can I rate-limit gns3_stop_all_nodes? +

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

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

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

Enforce policy on every GNS3 Network Simulator MCP Server tool call.

Start from GNS3 Network Simulator MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

42 GNS3 Network Simulator MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.