AI agents call export_bom to retrieve information from Kicad without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting a BOM as CSV is a read/export operation that retrieves existing component data from the design and outputs it in a structured format. It does not modify, delete, or execute anything, and has no financial or destructive implications.
From the tool's definition Export Bill of Materials (BOM) as CSV
Attacks that exploit this kind of access
Export Bill of Materials (BOM) as CSV. It is categorised as a Read tool in the Kicad MCP Server, which means it retrieves data without modifying state.
Register the Kicad MCP server in PolicyLayer and add a rule for export_bom: 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.
export_bom is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the export_bom 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 export_bom. 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.
export_bom 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 →