Export a Bill of Materials for a KiCad project. This tool attempts to generate a CSV BOM file for a KiCad project. It requires KiCad to be installed with the appropriate command-line tools. Args: project_path: Path to the KiCad project file (.kicad_pro) ctx: MCP context for progress reporting Ret...
AI agents use export_bom_csv to create or update resources in KiCad MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KiCad MCP Server environment.
This tool creates a new CSV file output (Write category) from existing KiCad project data. It does not execute arbitrary code, delete data, or cause financial effects. The blast radius is minimal—the worst outcome is an incorrectly formatted or corrupted CSV file, which is easily regenerated. No existing project data is modified or destroyed.
From the tool's definition Tool description states it 'Export a Bill of Materials' and 'generate a CSV BOM file', which creates/outputs a new file artifact from existing project data.
Documented attack patterns abuse exactly the kind of access export_bom_csv gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and KiCad MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for export_bom_csv:
{
"version": "1",
"default": "deny",
"tools": {
"export_bom_csv": {
"limits": [
{
"counter": "export_bom_csv_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_bom_csv stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Export a Bill of Materials for a KiCad project. This tool attempts to generate a CSV BOM file for a KiCad project. It requires KiCad to be installed with the appropriate command-line tools. Args: project_path: Path to the KiCad project file (.kicad_pro) ctx: MCP context for progress reporting Returns: Dictionary with export results. It is categorised as a Write tool in the KiCad MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the KiCad MCP Server MCP server in PolicyLayer and add a rule for export_bom_csv: 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 MCP Server. Nothing to install.
export_bom_csv 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 export_bom_csv 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_csv. 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_csv is provided by the KiCad MCP Server MCP server (lamaalrajih/kicad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from KiCad MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 KiCad MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.