AI agents use kicad.move_component 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.
Moving a component changes the state of the PCB design (coordinates, layout) but is fully reversible—the user can move it back or undo the action. This is a write operation, not destructive. Severity is medium because misuse could corrupt a PCB layout requiring rework, but the impact is limited to a single design artifact and can be corrected.
From the tool's definition Tool name 'move_component' and description 'Move a component to a new position' indicate a reversible modification of PCB design data. The action modifies component placement coordinates without deleting or permanently destroying data.
Attacks that exploit this kind of access
Move a component to a new position. 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.move_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 Eda. Nothing to install.
kicad.move_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 kicad.move_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 kicad.move_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.
kicad.move_component 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 →