Modify an existing trace (change width, layer, or net).
AI agents use modify_trace 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 trace properties (width, layer, net assignments) which are design parameters that can be undone or reverted in KiCAD. It does not delete traces (which would be Destructive), execute code (Execute), or move money (Financial).
From the tool's definition Tool name 'modify_trace' and description state it 'Modify an existing trace (change width, layer, or net)' — this reversibly alters PCB design data without deleting or executing arbitrary operations.
Documented attack patterns abuse exactly the kind of access modify_trace 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 modify_trace:
{
"version": "1",
"default": "deny",
"tools": {
"modify_trace": {
"limits": [
{
"counter": "modify_trace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} modify_trace 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.
Modify an existing trace (change width, layer, or net). 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 modify_trace: 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.
modify_trace 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 modify_trace 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 modify_trace. 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.
modify_trace 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.