AI agents use kicad.export_bom 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 a new file artifact (the BOM export) based on schematic data, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. While the BOM itself is read-only output, the act of exporting constitutes data generation/creation.
From the tool's definition Tool generates and exports a BOM (Bill of Materials) file from schematic data. The term 'export' combined with 'Bill of Materials' indicates creation of a new output file that represents schematic data in a structured format (typically CSV, XML, or other…
Attacks that exploit this kind of access
[Requires open project] Export Bill of Materials from the schematic. 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.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 Eda. Nothing to install.
kicad.export_bom 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.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 kicad.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.
kicad.export_bom 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 →