AI agents use set_board_size 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 modifies PCB board design data (board dimensions) which is a core design parameter. The operation is reversible—board size can be changed again—so it is Write rather than Destructive. The severity is medium because changing board size could break component placements or violate design constraints, but an AI agent could potentially recover or remediate such issues through subsequent tool calls.
From the tool's definition Tool name 'set_board_size' combined with description 'Set the size of the PCB board' indicates modification of board design parameters. This is a reversible configuration change to the PCB design.
Documented attack patterns abuse exactly the kind of access set_board_size 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 set_board_size:
{
"version": "1",
"default": "deny",
"tools": {
"set_board_size": {
"limits": [
{
"counter": "set_board_size_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_board_size 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.
Set the size of the PCB board. 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_size: 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_size 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_size 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_size. 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_size 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.
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.
157 KiCAD-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.