AI agents use kicad.add_wire to create or update resources in Eda — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Eda environment.
This tool creates new wires (electrical connections) in a KiCad schematic or PCB design, which modifies the design file reversibly. While the description is empty (lowering confidence slightly), the context and name clearly indicate a Write operation. It has medium severity because improper wiring could introduce design flaws, but changes can be undone through standard design tools.
From the tool's definition Tool name 'kicad.add_wire' indicates creation of circuit connections; sibling tools like 'kicad.add_component', 'kicad.add_line', 'kicad.add_net_label' confirm this is part of a schematic/PCB design interface that creates and modifies circuit elements.
Attacks that exploit this kind of access
kicad.add_wire. It is categorised as a Write tool in the Eda MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Eda MCP server in PolicyLayer and add a rule for kicad.add_wire: 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 Eda. Nothing to install.
kicad.add_wire 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 kicad.add_wire 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 kicad.add_wire. 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.
kicad.add_wire is provided by the Eda MCP server (saeronlab/eda-mcp). 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 →