batch_list_symbol_pins
Return pin names, numbers, types, and symbol-local coordinates for multiple symbols in a single call. Use instead of calling list_symbol_pins repeatedly when placing a subcircuit — saves 5–10 round-trips. Each result includes pins (with x/y/angle in symbol-local coords, Y-up per KiCAD lib convent...
This record as markdown: /tools/mixelpixx-kicad-mcp-server/batch-list-symbol-pins.md
What batch_list_symbol_pins does on KiCAD-MCP-Server
AI agents call batch_list_symbol_pins to retrieve information from KiCAD-MCP-Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why batch_list_symbol_pins is rated Low
This tool queries and retrieves symbol metadata (pin information and bounding boxes) without any side effects. It is a read-only data retrieval operation that supports design queries, fitting the 'Read' category of tools that retrieve or query data with no side effects. The low severity reflects that misuse would only affect information gathering, not design integrity or external systems.
From the tool's definition Tool returns pin names, numbers, types, and coordinates for multiple symbols. Description states 'Return pin names, numbers, types, and symbol-local coordinates' and 'Each result includes pins... and body_bbox'.
Attacks that exploit this kind of access
The rule that runs batch_list_symbol_pins 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_list_symbol_pins, this is the rule to start with:
batch_list_symbol_pins is read-only, so it stays allowed. 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_list_symbol_pins call is checked against it from then on.
Questions about batch_list_symbol_pins
Return pin names, numbers, types, and symbol-local coordinates for multiple symbols in a single call. Use instead of calling list_symbol_pins repeatedly when placing a subcircuit — saves 5–10 round-trips. Each result includes pins (with x/y/angle in symbol-local coords, Y-up per KiCAD lib convention) and body_bbox (bounding box of pin envelope ±1.27mm, symbol-local coords). IMPORTANT: coordinates are symbol-local (Y-up, pre-rotation); after placement use get_schematic_pin_locations for post-rotation schematic coordinates. Set compact=true for simple 2-pin passives (Device:R/C/L) to get just pin_count, body_bbox, and is_symmetric. It is categorised as a Read tool in the KiCAD-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for batch_list_symbol_pins: 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_list_symbol_pins is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the batch_list_symbol_pins 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_list_symbol_pins. 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_list_symbol_pins 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