AI agents use kicad.create_net_class to create or update resources in Eda — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Eda environment.
Net classes in KiCad are design parameters that can be created, modified, and deleted without permanent data loss. Creating a net class modifies the project file but does not destructively delete data or execute arbitrary code. This is a reversible Write operation typical of design tool workflows. Confidence is moderate due to the empty description limiting confirmation of exact semantics.
From the tool's definition Tool name 'create_net_class' indicates creation of a new net class object in KiCad, which modifies the design project state.
Attacks that exploit this kind of access
kicad.create_net_class. It is categorised as a Write tool in the Eda MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Eda MCP server in PolicyLayer and add a rule for kicad.create_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 Eda. Nothing to install.
kicad.create_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 kicad.create_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 kicad.create_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.
kicad.create_net_class is provided by the Eda MCP server (saeronlab/eda-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
kicad.create_net_class is one line of Eda's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →