export_topology_diagram
Export topology diagram to SVG/PNG files on disk. For agents: use diagrams://{project_id}/topology resource for direct access without saving files.
This record as markdown: /tools/chistokhinsv-gns3-mcp/export-topology-diagram.md
What export_topology_diagram does on GNS3 MCP Server
AI agents use export_topology_diagram to create or update resources in GNS3 MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GNS3 MCP Server environment.
Why export_topology_diagram is rated Medium
This tool creates new files on the filesystem, which is a Write operation that modifies system state. While file export itself is reversible (files can be deleted), it does write data to disk and occupies storage resources.
From the tool's definition Tool exports and saves topology diagram files to disk in SVG/PNG formats. The description explicitly states 'Export topology diagram to SVG/PNG files on disk', indicating file creation/writing operations.
Attacks that exploit this kind of access
The rule that runs export_topology_diagram 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 export_topology_diagram, this is the rule to start with:
export_topology_diagram stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GNS3 MCP Server, apply this rule, and every export_topology_diagram call is checked against it from then on.
Questions about export_topology_diagram
Export topology diagram to SVG/PNG files on disk. For agents: use diagrams://{project_id}/topology resource for direct access without saving files. It is categorised as a Write tool in the GNS3 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GNS3 MCP Server MCP server in PolicyLayer and add a rule for export_topology_diagram: 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.
export_topology_diagram is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_topology_diagram 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 export_topology_diagram. 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.
export_topology_diagram 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.
More on GNS3 MCP Server, and thousands of servers like it.
This server
Across the catalogue