export_position_file
Export a component placement/position file (pick-and-place) for PCB assembly in CSV or ASCII format.
This record as markdown: /tools/mixelpixx-kicad-mcp-server/export-position-file.md
What export_position_file does on KiCAD-MCP-Server
AI agents use export_position_file 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.
Why export_position_file is rated Medium
The tool creates/generates new data (a position/placement file) as output, which aligns with Write semantics. While it touches manufacturing data, it is not Destructive (not irreversible), not Execute (not running arbitrary code based on arguments), not Financial.
From the tool's definition Tool exports (generates and writes) component placement data to a file in CSV or ASCII format. The action is a creation of new data output but does not directly modify the KiCAD design or irreversibly delete anything.
Attacks that exploit this kind of access
The rule that runs export_position_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and KiCAD-MCP-Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For export_position_file, this is the rule to start with:
export_position_file 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.
The button opens the PolicyLayer dashboard: create your workspace, connect KiCAD-MCP-Server, apply this rule, and every export_position_file call is checked against it from then on.
Questions about export_position_file
Export a component placement/position file (pick-and-place) for PCB assembly in CSV or ASCII format. 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_position_file: 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_position_file 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_position_file 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_position_file. 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_position_file is provided by the KiCAD-MCP-Server MCP server (mixelpixx/kicad-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on KiCAD-MCP-Server, and thousands of servers like it.
This server
Across the catalogue