launch_kicad_ui
Launch KiCAD UI, optionally with a project file
This record as markdown: /tools/mixelpixx-kicad-mcp-server/launch-kicad-ui.md
What launch_kicad_ui does on KiCAD-MCP-Server
AI agents invoke launch_kicad_ui to trigger actions in KiCAD-MCP-Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why launch_kicad_ui is rated High
This tool executes an external application (KiCAD) whose behavior depends on provided arguments. While launching a UI itself is typically benign, the ability to specify a project file creates a potential attack surface if an adversary can control the file path argument (e.g., path traversal, loading malicious project files).
From the tool's definition Tool description states 'Launch KiCAD UI, optionally with a project file' - this launches an external application with potential user-supplied arguments (project file path).
Attacks that exploit this kind of access
The rule that runs launch_kicad_ui 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 launch_kicad_ui, this is the rule to start with:
launch_kicad_ui stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 launch_kicad_ui call is checked against it from then on.
Questions about launch_kicad_ui
Launch KiCAD UI, optionally with a project file. It is categorised as a Execute tool in the KiCAD-MCP-Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for launch_kicad_ui: 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.
launch_kicad_ui is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the launch_kicad_ui 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 launch_kicad_ui. 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.
launch_kicad_ui 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.
Across the catalogue