delete_schematic_component
Remove a placed symbol from a KiCAD schematic (.kicad_sch). This removes the symbol instance (the placed component) from the schematic. It does NOT remove the symbol definition from lib_symbols. With deleteAttachedLabels, net labels sitting exactly on the deleted component
This record as markdown: /tools/mixelpixx-kicad-mcp-server/delete-schematic-component.md
What delete_schematic_component does on KiCAD-MCP-Server
AI agents call delete_schematic_component 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.
Why delete_schematic_component is rated Critical
This tool permanently removes data (a schematic component instance) from a design file in an irreversible manner. While the symbol definition remains in the library, the placement instance and its associated metadata (including potentially net labels via deleteAttachedLabels) are deleted and cannot be undone programmatically. This fits the Destructive category as it involves irreversible deletion of design data.
From the tool's definition Tool name contains 'delete', description states 'Remove a placed symbol from a KiCAD schematic' and 'This removes the symbol instance'. The operation is irreversible—once deleted, the component placement is gone and must be re-added manually.
Attacks that exploit this kind of access
The rule that runs delete_schematic_component safely
PolicyLayer is an MCP gateway: it sits between your AI agents and KiCAD-MCP-Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_schematic_component, this is the rule to start with:
delete_schematic_component is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect KiCAD-MCP-Server, apply this rule, and every delete_schematic_component call is checked against it from then on.
Questions about delete_schematic_component
Remove a placed symbol from a KiCAD schematic (.kicad_sch). This removes the symbol instance (the placed component) from the schematic. It does NOT remove the symbol definition from lib_symbols. With deleteAttachedLabels, net labels sitting exactly on the deleted component. 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.
Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for delete_schematic_component: 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.
delete_schematic_component 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 delete_schematic_component 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 delete_schematic_component. 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.
delete_schematic_component 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.
More on KiCAD-MCP-Server, and thousands of servers like it.
Across the catalogue