AI agents use add_copper_zone to create or update resources in Kicad — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kicad environment.
Copper zones are PCB design elements that define conductive regions. Creating a copper zone modifies the PCB design reversibly but can have significant downstream effects on electrical connectivity, manufacturing, and circuit behavior if placed incorrectly. This is a Write operation (creates new design data) rather than Destructive (zones can be removed/edited).
From the tool's definition Tool name 'add_copper_zone' indicates creation of a copper zone on a PCB. Sibling tools on the same server (add_pcb_line, add_pcb_text, add_lib_symbol, add_label, etc.) are all write/create operations that modify design artifacts.
Attacks that exploit this kind of access
add_copper_zone. It is categorised as a Write tool in the Kicad MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kicad MCP server in PolicyLayer and add a rule for add_copper_zone: 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. Nothing to install.
add_copper_zone 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 add_copper_zone 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 add_copper_zone. 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.
add_copper_zone is provided by the Kicad MCP server (productofamerica/mcp-server-kicad). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →