route_pad_to_pad
PREFERRED tool for pad-to-pad routing. Looks up pad positions automatically, detects the net from the pad, and — critically — if the two pads are on different copper layers (e.g. J1 on F.Cu and J2 on B.Cu) automatically inserts a via at the midpoint so the connection is complete. Always use this ...
This record as markdown: /tools/mixelpixx-kicad-mcp-server/route-pad-to-pad.md
What route_pad_to_pad does on KiCAD-MCP-Server
AI agents use route_pad_to_pad 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 route_pad_to_pad is rated Medium
This tool creates or modifies traces and vias in a KiCAD PCB design, which are typical Write operations (reversible changes to design data). While it modifies circuit connectivity, it does not irreversibly delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). The recommendation to 'always use this instead of route_trace' indicates it is a primary design modification tool.
From the tool's definition Tool description states it performs pad-to-pad routing, automatically inserts vias, and creates connections in a PCB design—these are reversible modifications to the circuit layout.
Attacks that exploit this kind of access
The rule that runs route_pad_to_pad 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 route_pad_to_pad, this is the rule to start with:
route_pad_to_pad 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 route_pad_to_pad call is checked against it from then on.
Questions about route_pad_to_pad
PREFERRED tool for pad-to-pad routing. Looks up pad positions automatically, detects the net from the pad, and — critically — if the two pads are on different copper layers (e.g. J1 on F.Cu and J2 on B.Cu) automatically inserts a via at the midpoint so the connection is complete. Always use this instead of route_trace when routing between named component pads. 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 route_pad_to_pad: 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.
route_pad_to_pad 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 route_pad_to_pad 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 route_pad_to_pad. 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.
route_pad_to_pad 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