connect_to_net
Connect a component pin to a named net by adding a wire stub and net label at the exact pin endpoint.
This record as markdown: /tools/mixelpixx-kicad-mcp-server/connect-to-net.md
What connect_to_net does on KiCAD-MCP-Server
AI agents use connect_to_net 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 connect_to_net is rated Medium
This tool creates new schematic connections (wire stubs and net labels) in a KiCAD circuit design, modifying the design state. It is Write-category because: (1) it adds new objects reversibly, (2) effects can be undone in KiCAD's undo system, and (3) it does not execute external commands or irreversibly destroy data.
From the tool's definition Tool description states it connects a component pin to a net by 'adding a wire stub and net label' — explicit creation/modification of circuit schematic elements. This is reversible circuit design work.
Attacks that exploit this kind of access
The rule that runs connect_to_net 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 connect_to_net, this is the rule to start with:
connect_to_net 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 connect_to_net call is checked against it from then on.
Questions about connect_to_net
Connect a component pin to a named net by adding a wire stub and net label at the exact pin endpoint. 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 connect_to_net: 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.
connect_to_net 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 connect_to_net 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 connect_to_net. 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.
connect_to_net 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