AI agents use kicad.place_via 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.
The tool places a via (an electrical connection through PCB layers), which modifies the PCB design reversibly. This is a Write operation—it creates new design elements without deleting existing data or executing arbitrary code. Confidence is lowered from 0.85 to 0.75 due to the empty description, which prevents confirmation of exact behavior and parameters.
From the tool's definition Tool name 'kicad.place_via' and sibling tools that perform design operations (add_component, add_wire, add_line, annotate_schematic, create_board_outline) all create or modify PCB design data. 'Place' indicates adding a via to the board layout.
Attacks that exploit this kind of access
kicad.place_via. 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.place_via: 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.place_via 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.place_via 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.place_via. 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.place_via 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 →