get_pad_position
Return the exact XY position of a specific pad on a PCB component. Use this before routing to get accurate start/end coordinates.
This record as markdown: /tools/mixelpixx-kicad-mcp-server/get-pad-position.md
What get_pad_position does on KiCAD-MCP-Server
AI agents call get_pad_position 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_pad_position is rated Low
This tool retrieves positional metadata from a PCB design. It performs a read-only query to obtain pad coordinates for informational purposes (specifically mentioned for routing preparation). No data is created, modified, deleted, or executed. The operation is purely informational with no blast radius if an AI agent misuses it—it cannot cause unintended modifications to the PCB design or trigger external operations.
From the tool's definition Tool description states 'Return the exact XY position' - this is a query operation that retrieves data about pad coordinates without modifying, executing code, or causing side effects.
Attacks that exploit this kind of access
The rule that runs get_pad_position 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_pad_position, this is the rule to start with:
get_pad_position 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_pad_position call is checked against it from then on.
Questions about get_pad_position
Return the exact XY position of a specific pad on a PCB component. Use this before routing to get accurate start/end coordinates. 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_pad_position: 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_pad_position 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_pad_position 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_pad_position. 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_pad_position 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