export_dsn
Export the current PCB to Specctra DSN format. Useful for manual Freerouting workflow or external autorouters.
This record as markdown: /tools/mixelpixx-kicad-mcp-server/export-dsn.md
What export_dsn does on KiCAD-MCP-Server
AI agents use export_dsn to create or update resources in KiCAD-MCP-Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KiCAD-MCP-Server environment.
Why export_dsn is rated Medium
This tool exports (writes) PCB design data to an external file format (Specctra DSN) for use by external tools. While it creates/outputs data, it does not irreversibly delete or modify the original PCB design file—it generates a derived format for external consumption. This is reversible (the export can be re-run or deleted) and does not execute arbitrary code or commands, making it Write rather than Execute.
From the tool's definition Tool is named 'export_dsn' and described as 'Export the current PCB to Specctra DSN format.' The verb 'export' indicates creation of output data from the current PCB design state.
Attacks that exploit this kind of access
The rule that runs export_dsn safely
PolicyLayer is an MCP gateway: it sits between your AI agents and KiCAD-MCP-Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For export_dsn, this is the rule to start with:
export_dsn 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 KiCAD-MCP-Server, apply this rule, and every export_dsn call is checked against it from then on.
Questions about export_dsn
Export the current PCB to Specctra DSN format. Useful for manual Freerouting workflow or external autorouters. It is categorised as a Write tool in the KiCAD-MCP-Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for export_dsn: 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 KiCAD-MCP-Server. Nothing to install.
export_dsn 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_dsn 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_dsn. 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_dsn is provided by the KiCAD-MCP-Server MCP server (mixelpixx/kicad-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on KiCAD-MCP-Server, and thousands of servers like it.
This server
Across the catalogue