get_wire_connections
Returns the net name and all wires and component pins connected at a given point.
This record as markdown: /tools/mixelpixx-kicad-mcp-server/get-wire-connections.md
What get_wire_connections does on KiCAD-MCP-Server
AI agents call get_wire_connections 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_wire_connections is rated Low
This tool retrieves and queries circuit net connection information from the KiCAD design. It has no side effects and performs only read operations on the PCB design data. The context of sibling tools (which perform writes and create elements) reinforces that this tool is purely informational, making it a Read category tool with low severity.
From the tool's definition Tool description states 'Returns the net name and all wires and component pins connected at a given point' — the verb 'Returns' indicates data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs get_wire_connections 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_wire_connections, this is the rule to start with:
get_wire_connections 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_wire_connections call is checked against it from then on.
Questions about get_wire_connections
Returns the net name and all wires and component pins connected at a given point. 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_wire_connections: 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_wire_connections 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_wire_connections 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_wire_connections. 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_wire_connections 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