AI agents use place_component 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.
Placing components in a PCB or schematic design modifies the design file reversibly. This is a Write operation—the change can be undone/removed. While the tool description is empty (lowering confidence slightly), the name 'place_component' combined with the server's stated purpose of 'read/write' operations and the pattern of sibling 'add_*' tools clearly indicates data modification.
From the tool's definition Tool name 'place_component' and sibling tools like 'add_copper_zone', 'add_global_label', 'add_hierarchical_sheet', 'add_pcb_line' indicate component placement/modification capabilities in KiCad design files.
Attacks that exploit this kind of access
place_component. 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 place_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 Kicad. Nothing to install.
place_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 place_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 place_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.
place_component 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 →