get_schematic_pin_locations
Returns the exact x/y coordinates of every pin on a schematic component. Use this before add_schematic_net_label to place labels correctly on pin endpoints.
This record as markdown: /tools/mixelpixx-kicad-mcp-server/get-schematic-pin-locations.md
What get_schematic_pin_locations does on KiCAD-MCP-Server
AI agents call get_schematic_pin_locations 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 get_schematic_pin_locations is rated Low
This tool retrieves geometric/positional data from an existing schematic without creating, modifying, deleting, or executing any operations. It is purely informational in nature, used to support placement decisions in subsequent operations. The low severity reflects that misuse would only result in incorrect read operations or position data, not destructive or irreversible changes to the design.
From the tool's definition The tool description states it 'Returns the exact x/y coordinates' of schematic component pins. The verb 'Returns' indicates data retrieval with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_schematic_pin_locations 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 get_schematic_pin_locations, this is the rule to start with:
get_schematic_pin_locations 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 get_schematic_pin_locations call is checked against it from then on.
Questions about get_schematic_pin_locations
Returns the exact x/y coordinates of every pin on a schematic component. Use this before add_schematic_net_label to place labels correctly on pin endpoints. 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 get_schematic_pin_locations: 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.
get_schematic_pin_locations 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 get_schematic_pin_locations 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 get_schematic_pin_locations. 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.
get_schematic_pin_locations 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