remove_dangling_tracks
AI agents call remove_dangling_tracks to permanently remove resources in Kicad — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing dangling tracks from a PCB design is likely irreversible without undo history, as it deletes track segments. The description is empty, which lowers confidence, but the name strongly implies a destructive cleanup operation. Given the PCB design context and sibling tools that add/modify elements, this tool likely permanently removes unconnected track stubs.
From the tool's definition Tool name 'remove_dangling_tracks' — 'remove' implies deletion of PCB track segments; 'dangling' suggests incomplete/unconnected tracks.
Attacks that exploit this kind of access
remove_dangling_tracks. It is categorised as a Destructive tool in the Kicad MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kicad MCP server in PolicyLayer and add a rule for remove_dangling_tracks: 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. Nothing to install.
remove_dangling_tracks is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_dangling_tracks 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 remove_dangling_tracks. 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.
remove_dangling_tracks is provided by the Kicad MCP server (productofamerica/mcp-server-kicad). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →