Launch KiCAD UI, optionally with a project file
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.
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).
Documented attack patterns abuse exactly the kind of access launch_kicad_ui 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 launch_kicad_ui:
{
"version": "1",
"default": "deny",
"tools": {
"launch_kicad_ui": {
"limits": [
{
"counter": "launch_kicad_ui_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
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.
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.