move_hierarchical_sheet · Kicad MCP: Risk & Policy

WHAT IT DOES

What move_hierarchical_sheet does on Kicad

AI agents use move_hierarchical_sheet to create or update resources in Kicad — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kicad environment.

WHY IT NEEDS A POLICY

Why move_hierarchical_sheet needs a policy

Moving a hierarchical sheet is a reversible modification to the schematic design (changing position/coordinates). It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not involve financial transactions (ruling out Financial). Write is the appropriate category as it modifies design artifacts.

From the tool's definition Tool description states 'Move a hierarchical sheet block to a new position, including all pins' — a modification operation that changes the spatial layout of schematic elements.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_hierarchical_sheet Rate-limited

move_hierarchical_sheet stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_hierarchical_sheet": {
      "limits": [
        {
          "counter": "move_hierarchical_sheet_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kicad, so you can run agents against it safely.

FAQ

Questions about move_hierarchical_sheet

What does the move_hierarchical_sheet tool do? +

Move a hierarchical sheet block to a new position, including all pins. It is categorised as a Write tool in the Kicad MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_hierarchical_sheet? +

Register the Kicad MCP server in PolicyLayer and add a rule for move_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.

What risk level is move_hierarchical_sheet? +

move_hierarchical_sheet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit move_hierarchical_sheet? +

Yes. Add a rate_limit block to the move_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.

How do I block move_hierarchical_sheet completely? +

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

What MCP server provides move_hierarchical_sheet? +

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