AI agents use kicad.add_no_connect 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 or modifies schematic annotations reversibly. While it changes design validation state, it does not execute arbitrary commands, delete data, or cause irreversible changes. The modification can be undone by removing the flag. This is a Write operation typical of PCB design tools that create or update design elements.
From the tool's definition Tool marks an unused pin with a no-connect flag, modifying schematic state. The description explicitly indicates it changes ERC (Electrical Rule Check) validation status by adding a flag to the design.
Attacks that exploit this kind of access
Mark an unused pin with a no-connect flag. Required to pass ERC. 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_no_connect: 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_no_connect 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_no_connect 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_no_connect. 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_no_connect 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 →