duplicate_component
Duplicate an existing PCB component at an offset position, optionally with a new reference designator.
This record as markdown: /tools/mixelpixx-kicad-mcp-server/duplicate-component.md
What duplicate_component does on KiCAD-MCP-Server
AI agents use duplicate_component 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 duplicate_component is rated Medium
This tool creates new data (duplicated components) in the PCB design file. The operation is reversible—duplicated components can be deleted or the file can be reverted. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial). It modifies the PCB design by adding components, making it a Write operation.
From the tool's definition Tool description states it will 'Duplicate an existing PCB component at an offset position, optionally with a new reference designator.' The words 'duplicate' and 'offset position' indicate creation of new component instances in the PCB design, which is a…
Attacks that exploit this kind of access
The rule that runs duplicate_component 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 duplicate_component, this is the rule to start with:
duplicate_component 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 duplicate_component call is checked against it from then on.
Questions about duplicate_component
Duplicate an existing PCB component at an offset position, optionally with a new reference designator. 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 duplicate_component: 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.
duplicate_component 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 duplicate_component 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 duplicate_component. 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.
duplicate_component 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