batch_move_components

Move multiple PCB components transactionally. If one reference/spec is invalid, no components are moved. Saves by default unless save=false.

SERVERKiCAD-MCP-Server SOURCEmixelpixx/kicad-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mixelpixx-kicad-mcp-server/batch-move-components.md

WHAT IT DOES

What batch_move_components does on KiCAD-MCP-Server

AI agents use batch_move_components to create or update resources in KiCAD-MCP-Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KiCAD-MCP-Server environment.

RISK

Why batch_move_components is rated Medium

This tool creates or modifies data reversibly. It repositions components on a PCB schematic/layout and saves the changes to the design file. While the changes are persistent, they are not destructive (components are not deleted, and moves can be undone in KiCAD).

From the tool's definition Tool description states 'Move multiple PCB components transactionally' and 'Saves by default unless save=false' — modifies PCB layout data and persists changes.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs batch_move_components safely

PolicyLayer is an MCP gateway: it sits between your AI agents and KiCAD-MCP-Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For batch_move_components, this is the rule to start with:

batch_move_components Rate-limited

batch_move_components 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": {
    "batch_move_components": {
      "limits": [
        {
          "counter": "batch_move_components_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect KiCAD-MCP-Server, apply this rule, and every batch_move_components call is checked against it from then on.

FAQ

Questions about batch_move_components

What does the batch_move_components tool do? +

Move multiple PCB components transactionally. If one reference/spec is invalid, no components are moved. Saves by default unless save=false. It is categorised as a Write tool in the KiCAD-MCP-Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on batch_move_components? +

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

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

Can I rate-limit batch_move_components? +

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

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

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

KEEP EXPLORING

More on KiCAD-MCP-Server, and thousands of servers like it.

This server

All 231 KiCAD-MCP-Server tools →

Across the catalogue

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →