kicad_delete_component
Delete a component from the board.
This record as markdown: /tools/altium-mcp-suite/kicad-delete-component.md
What kicad_delete_component does on Altium-MCP-Suite
AI agents call kicad_delete_component to permanently remove resources in Altium-MCP-Suite, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why kicad_delete_component is rated Critical
Permanently removes board components without undo possibility; significant design damage if misused.
From the tool's definition Delete a component from the board irreversibly.
Attacks that exploit this kind of access
The rule that runs kicad_delete_component safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Altium-MCP-Suite, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kicad_delete_component, this is the rule to start with:
kicad_delete_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 Altium-MCP-Suite, apply this rule, and every kicad_delete_component call is checked against it from then on.
Questions about kicad_delete_component
Delete a component from the board. It is categorised as a Destructive tool in the Altium-MCP-Suite MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Altium-MCP-Suite MCP server in PolicyLayer and add a rule for kicad_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 Altium-MCP-Suite. Nothing to install.
kicad_delete_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 kicad_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.
Set action: deny in the PolicyLayer policy for kicad_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.
kicad_delete_component is provided by the Altium-MCP-Suite MCP server (M-R-Abedini/Altium-MCP-Suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Altium-MCP-Suite, and thousands of servers like it.
Across the catalogue