Return the exact XY position of a specific pad on a PCB component. Use this before routing to get accurate start/end coordinates.
AI agents call get_pad_position to retrieve information from KiCAD-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access get_pad_position 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 get_pad_position:
{
"version": "1",
"default": "deny",
"tools": {
"get_pad_position": {}
}
} get_pad_position is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.