New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_component

Remove a component from the PCB by its reference designator.

SERVERKiCAD-MCP-Server SOURCEmixelpixx/kicad-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mixelpixx-kicad-mcp-server/delete-component.md

What delete_component does on KiCAD-MCP-Server

AI agents call delete_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_component is rated Critical

This tool performs an irreversible deletion operation on PCB design data. Removing a component cannot be easily undone and represents a destructive modification to the board design.

From the tool's definition Tool name contains 'delete' and description states 'Remove a component from the PCB by its reference designator.' The action irreversibly removes a component from the circuit board design.

Questions about delete_component

What does the delete_component tool do? +

Remove a component from the PCB by its reference designator. 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_component? +

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

What risk level is delete_component? +

delete_component 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_component? +

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

How do I block delete_component completely? +

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

What MCP server provides delete_component? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of KiCAD-MCP-Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.