List all links (connections) in a project.
AI agents call gns3_list_links 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.
This tool performs a read-only operation—it queries and returns information about network links in a GNS3 project. There are no side effects, no data modification, and no external command execution. It belongs in the Read category with low severity since misuse would only expose existing topology information without enabling destructive or hazardous actions.
From the tool's definition Tool name 'gns3_list_links' and description 'List all links (connections) in a project' indicate a query operation that retrieves and displays existing network connection data without modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access gns3_list_links gives an agent:
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_links:
{
"version": "1",
"default": "deny",
"tools": {
"gns3_list_links": {}
}
} gns3_list_links is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all links (connections) in a project. It is categorised as a Read tool in the GNS3 Network Simulator MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GNS3 Network Simulator MCP Server MCP server in PolicyLayer and add a rule for gns3_list_links: 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.
gns3_list_links is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gns3_list_links 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.
Set action: deny in the PolicyLayer policy for gns3_list_links. 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.
gns3_list_links 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.
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.
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.