gns3_delete_node

THE RISK

Critical Risk

Why gns3_delete_node needs a policy

This tool irreversibly removes network simulation components (nodes) from an active GNS3 project. Deletion of project elements is an irreversible operation that constitutes destructive action. While GNS3 may support undo via snapshots, the tool itself performs permanent removal of data.

From the tool's definition Tool name 'gns3_delete_node' explicitly contains 'delete'. Description states 'Delete a node from the project' — a permanent removal operation that cannot be trivially undone without restoring from a snapshot.

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

POLICY

How to control gns3_delete_node

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_delete_node:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "gns3_delete_node"
  ]
}

gns3_delete_node disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT 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_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. Execute gns3_start_node Start a specific node.

All 42 GNS3 Network Simulator MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in GNS3 Network Simulator MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-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.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about gns3_delete_node

What does the gns3_delete_node tool do? +

Delete a node from the project. It is categorised as a Destructive tool in the GNS3 Network Simulator MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on gns3_delete_node? +

Register the GNS3 Network Simulator MCP Server MCP server in PolicyLayer and add a rule for gns3_delete_node: 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_delete_node? +

gns3_delete_node is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gns3_delete_node? +

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

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

gns3_delete_node 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 →