Set the currently active PCB layer by name (e.g. F.Cu, B.Cu).
AI agents use set_active_layer 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 application state (active layer selection) which affects subsequent operations and is reversible—users can switch to a different layer. It does not execute arbitrary commands, delete data, or cause financial impact.
From the tool's definition Tool sets/modifies the active PCB layer state by name (e.g. 'F.Cu, B.Cu'), which changes the current editing context in KiCAD but does not delete or irreversibly destroy data.
Documented attack patterns abuse exactly the kind of access set_active_layer 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_active_layer:
{
"version": "1",
"default": "deny",
"tools": {
"set_active_layer": {
"limits": [
{
"counter": "set_active_layer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_active_layer 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 currently active PCB layer by name (e.g. F.Cu, B.Cu). 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_active_layer: 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_active_layer 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_active_layer 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_active_layer. 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_active_layer 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.