export_netlist
Export the schematic netlist to a file using kicad-cli. Supports KiCad XML (default), Spice (for simulation), Cadstar, and OrcadPCB2 formats. Use this when you need to write a netlist file to disk — for example to produce a SPICE file for simulation or to diff against a reference. To get net/comp...
This record as markdown: /tools/mixelpixx-kicad-mcp-server/export-netlist.md
What export_netlist does on KiCAD-MCP-Server
AI agents use export_netlist 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_netlist is rated Medium
This tool creates or writes netlist files to disk in various formats (XML, Spice, Cadstar, OrcadPCB2). While it exports data rather than modifying the schematic itself, the act of writing files to disk constitutes a Write operation.
From the tool's definition Tool description states 'Export the schematic netlist to a file' and 'to write a netlist file to disk', indicating file creation/modification operations.
Attacks that exploit this kind of access
The rule that runs export_netlist 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_netlist, this is the rule to start with:
export_netlist 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_netlist call is checked against it from then on.
Questions about export_netlist
Export the schematic netlist to a file using kicad-cli. Supports KiCad XML (default), Spice (for simulation), Cadstar, and OrcadPCB2 formats. Use this when you need to write a netlist file to disk — for example to produce a SPICE file for simulation or to diff against a reference. To get net/component data inline without writing a file, use generate_netlist instead. 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_netlist: 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_netlist 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_netlist 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_netlist. 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_netlist 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