set_board_origin
Set the auxiliary (drill/place) origin and/or grid origin of a .kicad_pcb.
This record as markdown: /tools/mixelpixx-kicad-mcp-server/set-board-origin.md
What set_board_origin does on KiCAD-MCP-Server
AI agents use set_board_origin 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 set_board_origin is rated Medium
This tool modifies board configuration settings in a KiCAD PCB file. While it changes data that influences manufacturing (drill positions, part placement coordinates), these changes are reversible through subsequent edits or undo operations—the user can simply reset the origin/grid to different values. This places it in the Write category rather than Destructive.
From the tool's definition Tool description states it 'Set[s] the auxiliary (drill/place) origin and/or grid origin of a .kicad_pcb.' This modifies PCB file properties (origin and grid settings) which are design parameters that affect manufacturing output but are reversible.
Attacks that exploit this kind of access
The rule that runs set_board_origin 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 set_board_origin, this is the rule to start with:
set_board_origin 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 set_board_origin call is checked against it from then on.
Questions about set_board_origin
Set the auxiliary (drill/place) origin and/or grid origin of a .kicad_pcb. 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 set_board_origin: 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.
set_board_origin 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 set_board_origin 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 set_board_origin. 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.
set_board_origin 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