batch_add_no_connects
Add no-connect (X) flags to multiple pins in one call, to mark intentionally unconnected pins and silence ERC.
This record as markdown: /tools/mixelpixx-kicad-mcp-server/batch-add-no-connects.md
What batch_add_no_connects does on KiCAD-MCP-Server
AI agents use batch_add_no_connects 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_add_no_connects is rated Medium
This tool modifies design metadata (no-connect flags on pins) but does not destroy data or execute arbitrary operations. The changes are reversible, making it Write rather than Destructive. Blast radius is medium because incorrect bulk application could require manual remediation across many pins, but the operation itself doesn't delete data or cause irreversible harm to the board design.
From the tool's definition Tool name 'batch_add_no_connects' and description 'Add no-connect (X) flags to multiple pins in one call' explicitly indicates creation/modification of pin properties in KiCAD design. The action is reversible (flags can be removed or modified later).
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_add_no_connects 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_add_no_connects, this is the rule to start with:
batch_add_no_connects 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_add_no_connects call is checked against it from then on.
Questions about batch_add_no_connects
Add no-connect (X) flags to multiple pins in one call, to mark intentionally unconnected pins and silence ERC. 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_add_no_connects: 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_add_no_connects 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_add_no_connects 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_add_no_connects. 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_add_no_connects 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