connect_passthrough
Connects all pins of a source connector (e.g. J1) to matching pins of a target connector (e.g. J2) via shared net labels — pin N gets net
This record as markdown: /tools/mixelpixx-kicad-mcp-server/connect-passthrough.md
What connect_passthrough does on KiCAD-MCP-Server
AI agents use connect_passthrough 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_passthrough is rated Medium
This tool modifies the circuit topology by creating net connections between connector pins. While it changes design data, these modifications are reversible (nets can be disconnected, relabeled, or reconnected). The blast radius is medium because incorrect connector mapping could cause electrical shorts or non-functional circuits, but the change is not destructive (no data loss) and not financial.
From the tool's definition The tool 'connects all pins of a source connector...to matching pins of a target connector via shared net labels' — this creates or modifies electrical net connections in the PCB design, which is a reversible change to the design data.
Attacks that exploit this kind of access
The rule that runs connect_passthrough 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_passthrough, this is the rule to start with:
connect_passthrough 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_passthrough call is checked against it from then on.
Questions about connect_passthrough
Connects all pins of a source connector (e.g. J1) to matching pins of a target connector (e.g. J2) via shared net labels — pin N gets net. 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_passthrough: 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_passthrough 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_passthrough 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_passthrough. 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_passthrough 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