batch_set_schematic_property_positions
Move many Reference/Value field labels in a single file read/write — far faster than repeated set_schematic_property_position calls. Pass an
This record as markdown: /tools/mixelpixx-kicad-mcp-server/batch-set-schematic-property-positions.md
What batch_set_schematic_property_positions does on KiCAD-MCP-Server
AI agents use batch_set_schematic_property_positions 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.
Why batch_set_schematic_property_positions is rated Medium
This tool updates positions of schematic property labels (Reference/Value fields) in a reversible manner. It creates or modifies data but does not execute arbitrary code, delete data irreversibly, or move financial resources.
From the tool's definition Tool description states 'file read/write' and 'Move many Reference/Value field labels' — operations that modify schematic properties without deleting or destroying data.
Attacks that exploit this kind of access
The rule that runs batch_set_schematic_property_positions 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_set_schematic_property_positions, this is the rule to start with:
batch_set_schematic_property_positions 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.
The button opens the PolicyLayer dashboard: create your workspace, connect KiCAD-MCP-Server, apply this rule, and every batch_set_schematic_property_positions call is checked against it from then on.
Questions about batch_set_schematic_property_positions
Move many Reference/Value field labels in a single file read/write — far faster than repeated set_schematic_property_position calls. Pass an. 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.
Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for batch_set_schematic_property_positions: 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.
batch_set_schematic_property_positions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the batch_set_schematic_property_positions 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 batch_set_schematic_property_positions. 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.
batch_set_schematic_property_positions 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.
More on KiCAD-MCP-Server, and thousands of servers like it.
This server
Across the catalogue