Critical Risk →

remove_schematic_component_property

Remove a single custom property from a placed schematic symbol. Built-in fields (Reference, Value, Footprint, Datasheet) cannot be removed — KiCad requires them on every symbol. To clear a built-in field, use edit_schematic_component and set its value to an empty string.

How to control remove_schematic_component_property ↓

What remove_schematic_component_property does on KiCAD-MCP-Server

AI agents call remove_schematic_component_property 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 remove_schematic_component_property needs a policy

This tool irreversibly removes a custom property from a schematic symbol. Unlike editing (which is reversible by editing back), removal of a property destroys that data. Without an explicit undo mechanism in the MCP context, this constitutes a destructive operation. Severity is medium as it affects a single property on a single component rather than entire files or boards.

From the tool's definition Remove a single custom property from a placed schematic symbol

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

How to control remove_schematic_component_property

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

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

remove_schematic_component_property 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 remove_schematic_component_property

What does the remove_schematic_component_property tool do? +

Remove a single custom property from a placed schematic symbol. Built-in fields (Reference, Value, Footprint, Datasheet) cannot be removed — KiCad requires them on every symbol. To clear a built-in field, use edit_schematic_component and set its value to an empty string. 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 remove_schematic_component_property? +

Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for remove_schematic_component_property: 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 remove_schematic_component_property? +

remove_schematic_component_property 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 remove_schematic_component_property? +

Yes. Add a rate_limit block to the remove_schematic_component_property 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 remove_schematic_component_property completely? +

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

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