Remove label from schematic
AI agents call remove_label to permanently remove resources in KiCAD Schematic Manipulation MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a label from a schematic is a destructive operation; once deleted, the label (and any associated net connectivity information) is gone and cannot be undone through the tool itself. This could break net connections or signal naming in the schematic, making it a medium-severity destructive action.
From the tool's definition 'Remove label from schematic' — the word 'remove' indicates irreversible deletion of a schematic element
Attacks that exploit this kind of access
Remove label from schematic. It is categorised as a Destructive tool in the KiCAD Schematic Manipulation MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the KiCAD Schematic Manipulation MCP Server 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 Schematic Manipulation MCP Server. 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 Schematic Manipulation MCP Server MCP server (richard-luc/kicad-schematic-manipulation). 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 →