Critical Risk →

delete_component

Remove a component from the PCB by its reference designator.

How to control delete_component ↓

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.

Critical Risk

Why delete_component needs a policy

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.

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

How to control delete_component

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

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

delete_component 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_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.

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.