Remove a junction at the given coordinates.
AI agents call remove_junction 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.
This tool irreversibly deletes a junction from a KiCad schematic at specified coordinates. Junctions are critical circuit elements that define electrical connections between net segments. Removing a junction cannot be undone programmatically by the tool itself and will alter the circuit's topology and connectivity, potentially breaking the design.
From the tool's definition Tool name: 'remove_junction' with description 'Remove a junction at the given coordinates.' The verb 'remove' indicates deletion of a circuit element.
Attacks that exploit this kind of access
Remove a junction at the given coordinates. 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_junction: 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_junction 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_junction 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_junction. 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_junction 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 →