Copy routing pattern (traces and vias) from a group of source components to a matching group of target components. The offset is calculated automatically from the position difference between the first source and first target component. Useful for replicating routing between identical circuit blocks.
AI agents use copy_routing_pattern 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.
This tool creates and modifies PCB routing patterns (traces and vias) in a KiCAD project. While the modifications are theoretically reversible via undo, the tool directly alters the board design state. It does not delete or destroy existing data irreversibly, so it does not qualify as Destructive. It does not execute arbitrary code or external processes, so it does not qualify as Execute.
From the tool's definition The tool description states it will "Copy routing pattern (traces and vias)" from source to target components, which modifies the PCB design by adding traces and vias to the target location. This is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access copy_routing_pattern 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 copy_routing_pattern:
{
"version": "1",
"default": "deny",
"tools": {
"copy_routing_pattern": {
"limits": [
{
"counter": "copy_routing_pattern_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}copy_routing_pattern 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.
Free to start. No card required.
Copy routing pattern (traces and vias) from a group of source components to a matching group of target components. The offset is calculated automatically from the position difference between the first source and first target component. Useful for replicating routing between identical circuit blocks. 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 copy_routing_pattern: 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.
copy_routing_pattern 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 copy_routing_pattern 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 copy_routing_pattern. 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.
copy_routing_pattern 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.