get_jlcpcb_part
Get detailed information about a specific JLCPCB part by LCSC number. When JLCPCB Open Platform credentials are configured (JLCPCB_APP_ID / JLCPCB_API_KEY / JLCPCB_API_SECRET, e.g. in a project-root .env), this performs a REAL-TIME lookup — live stock, tiered pricing, parameters and library type ...
This record as markdown: /tools/mixelpixx-kicad-mcp-server/get-jlcpcb-part.md
What get_jlcpcb_part does on KiCAD-MCP-Server
AI agents call get_jlcpcb_part 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_jlcpcb_part is rated Low
This tool queries an external API or local database to retrieve part information (stock, pricing, parameters). It has no side effects on the KiCAD project or external systems—it only reads and returns data. The severity is low because misuse would only expose pricing/availability information without damaging data or triggering unintended operations.
From the tool's definition Tool performs a lookup operation: 'Get detailed information about a specific JLCPCB part by LCSC number' and 'performs a REAL-TIME lookup — live stock, tiered pricing, parameters and library type'. It retrieves data with a fallback to a snapshot database.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_jlcpcb_part 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_jlcpcb_part, this is the rule to start with:
get_jlcpcb_part 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_jlcpcb_part call is checked against it from then on.
Questions about get_jlcpcb_part
Get detailed information about a specific JLCPCB part by LCSC number. When JLCPCB Open Platform credentials are configured (JLCPCB_APP_ID / JLCPCB_API_KEY / JLCPCB_API_SECRET, e.g. in a project-root .env), this performs a REAL-TIME lookup — live stock, tiered pricing, parameters and library type — and falls back to the local snapshot database if the API call fails or no credentials are set. The response reports which backend answered via. 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_jlcpcb_part: 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_jlcpcb_part 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_jlcpcb_part 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_jlcpcb_part. 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_jlcpcb_part 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