Create a named net class with specific design rules (clearance, track width, via size) and assign nets to it.
AI agents use add_net_class 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 or modifies design rule configurations in a KiCAD project. While it does not delete data (thus not Destructive) or execute arbitrary code (thus not Execute), it writes new structured data (net classes and rule associations) into the project.
From the tool's definition Tool creates a new net class with design rules (clearance, track width, via size) and assigns nets—a reversible modification of circuit design parameters that persists in the PCB project.
Documented attack patterns abuse exactly the kind of access add_net_class 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 add_net_class:
{
"version": "1",
"default": "deny",
"tools": {
"add_net_class": {
"limits": [
{
"counter": "add_net_class_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_net_class 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.
Create a named net class with specific design rules (clearance, track width, via size) and assign nets to it. 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 add_net_class: 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.
add_net_class 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 add_net_class 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 add_net_class. 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.
add_net_class 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.