Add no-connect (X) flags to multiple pins in one call, to mark intentionally unconnected pins and silence ERC.
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.
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
Documented attack patterns abuse exactly the kind of access batch_add_no_connects gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and KiCAD-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_add_no_connects:
{
"version": "1",
"default": "deny",
"tools": {
"batch_add_no_connects": {
"limits": [
{
"counter": "batch_add_no_connects_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
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.
Start from KiCAD-MCP-Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
157 KiCAD-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.