Return a structured JSON netlist from the schematic — component list (reference, value, footprint) and net list (net name with all connected component/pin pairs). Use this to inspect or verify connectivity within the conversation. Does not write any file. To export a netlist file in Spice, KiCad ...
AI agents call generate_netlist to retrieve information from KiCAD-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only reads and returns schematic data as structured JSON. It explicitly states it does not write any file and is intended for inspection/verification purposes only.
From the tool's definition 'Return a structured JSON netlist from the schematic', 'Does not write any file', 'Use this to inspect or verify connectivity'
Documented attack patterns abuse exactly the kind of access generate_netlist gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and KiCAD-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_netlist:
{
"version": "1",
"default": "deny",
"tools": {
"generate_netlist": {}
}
} generate_netlist 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.
Return a structured JSON netlist from the schematic — component list (reference, value, footprint) and net list (net name with all connected component/pin pairs). Use this to inspect or verify connectivity within the conversation. Does not write any file. To export a netlist file in Spice, KiCad XML, Cadstar, or OrcadPCB2 format, use export_netlist instead. It is categorised as a Read tool in the KiCAD-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for generate_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.
generate_netlist 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 generate_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 generate_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.
generate_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.
Start from KiCAD-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.
157 KiCAD-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.