gns3_list_computes · GNS3 Network Simulator MCP Server MCP

WHAT IT DOES

What gns3_list_computes does on GNS3 Network Simulator MCP Server

AI agents call gns3_list_computes to retrieve information from GNS3 Network Simulator MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why gns3_list_computes needs a policy

This tool retrieves information about available compute servers without modifying, executing, or deleting anything. It is a straightforward query operation. The blast radius is minimal—an AI agent listing compute servers poses no security risk beyond potentially informing reconnaissance, which is low-impact in isolation.

From the tool's definition Tool name 'gns3_list_computes' and description 'List all available compute servers' indicate a retrieval/query operation with no side effects. The verb 'list' and the read-only nature of enumerating compute resources confirm this is a data retrieval function.

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

POLICY

How to control gns3_list_computes

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gns3_list_computes": {}
  }
}

gns3_list_computes is read-only, so it stays allowed — but 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.

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

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about gns3_list_computes

What does the gns3_list_computes tool do? +

List all available compute servers (local, VMs, remote). It is categorised as a Read tool in the GNS3 Network Simulator MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gns3_list_computes? +

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

gns3_list_computes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gns3_list_computes? +

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

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

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