remove_label
AI agents call remove_label 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.
The tool performs an irreversible deletion of a label from a KiCad project. Labels are critical to schematic documentation and PCB design; their removal cannot be undone without manual restoration. This fits the Destructive category (irreversible data deletion). While confidence is not absolute due to the empty description, the verb 'remove' combined with the KiCad design context makes destructive intent clear.
From the tool's definition Tool named 'remove_label' with no description provided. In the context of KiCad PCB/schematic design, 'remove' operations irreversibly delete design elements. Sibling tools like 'add_label', 'add_lib_symbol', etc.
Attacks that exploit this kind of access
remove_label. 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_label: 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_label 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_label 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_label. 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_label 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 →