search_parts_registry
Search an open, gate-verified parts registry for existing KiCAD parts BEFORE generating a custom footprint/symbol from scratch. Complements search_jlcpcb_parts: use that tool for JLCPCB sourcing data (price, stock, assembly tier); use this one to fetch a verified existing footprint/symbol/3D bund...
This record as markdown: /tools/mixelpixx-kicad-mcp-server/search-parts-registry.md
What search_parts_registry does on KiCAD-MCP-Server
AI agents call search_parts_registry 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 search_parts_registry is rated Low
This tool retrieves and queries data from an open parts registry (PartReel) with no side effects. It matches the 'Read' category as a search/fetch operation that does not create, modify, delete, or execute any operations. Severity is low because searching a public registry poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Search[es]' a parts registry and 'fetch[es]' verified footprints/symbols/3D bundles. No modification, deletion, or execution of external operations described. Read-only query against a public registry.
Attacks that exploit this kind of access
The rule that runs search_parts_registry 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 search_parts_registry, this is the rule to start with:
search_parts_registry 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 search_parts_registry call is checked against it from then on.
Questions about search_parts_registry
Search an open, gate-verified parts registry for existing KiCAD parts BEFORE generating a custom footprint/symbol from scratch. Complements search_jlcpcb_parts: use that tool for JLCPCB sourcing data (price, stock, assembly tier); use this one to fetch a verified existing footprint/symbol/3D bundle. Default registry: PartReel (https://partreel.com) — 18k+ verified parts, no auth. Override with the PARTREEL_API_BASE environment variable to point at any compatible registry. Matches are case-insensitive substrings over the part name, keywords, family, and manufacturer. 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 search_parts_registry: 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.
search_parts_registry 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 search_parts_registry 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 search_parts_registry. 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.
search_parts_registry 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