Critical Risk →

delete_trace

Delete traces from the PCB. Can delete by UUID, position, or bulk-delete all traces on a net.

How to control delete_trace ↓

What delete_trace does on KiCAD-MCP-Server

AI agents call delete_trace to permanently remove resources in KiCAD-MCP-Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_trace needs a policy

This tool irreversibly removes traces from a PCB layout. While not as critical as deleting an entire board design, trace deletion cannot be undone and represents permanent loss of design work. The capability to bulk-delete all traces on a net amplifies the blast radius.

From the tool's definition Tool name contains "delete" and description explicitly states "Delete traces from the PCB." This action "cannot be undone" as per the Destructive category definition.

Documented attack patterns abuse exactly the kind of access delete_trace gives an agent:

How to control delete_trace

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 delete_trace:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_trace"
  ]
}

delete_trace disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register KiCAD-MCP-Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_trace

What does the delete_trace tool do? +

Delete traces from the PCB. Can delete by UUID, position, or bulk-delete all traces on a net. It is categorised as a Destructive tool in the KiCAD-MCP-Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_trace? +

Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for delete_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.

What risk level is delete_trace? +

delete_trace is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_trace? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_trace completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_trace? +

delete_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.

Enforce policy on every KiCAD-MCP-Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.