remove_hierarchical_sheet
AI agents call remove_hierarchical_sheet 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 action of removing a hierarchical sheet from a KiCad project is irreversible—sheets once deleted cannot be automatically recovered, and this can cause loss of significant design work including all nets, symbols, and connections within that sheet. This meets the Destructive category definition of irreversibly deleting data.
From the tool's definition Tool name 'remove_hierarchical_sheet' indicates deletion/removal of a hierarchical sheet from a KiCad schematic project. In the context of KiCad design automation, removing sheets irreversibly deletes schematic structure and associated design data.
Attacks that exploit this kind of access
remove_hierarchical_sheet. 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_hierarchical_sheet: 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_hierarchical_sheet 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_hierarchical_sheet 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_hierarchical_sheet. 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_hierarchical_sheet 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 →