install_gui_driver

Deploy the in-KiCad GUI-driver helper plugin into the user

SERVERKiCAD-MCP-Server SOURCEmixelpixx/kicad-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mixelpixx-kicad-mcp-server/install-gui-driver.md

WHAT IT DOES

What install_gui_driver does on KiCAD-MCP-Server

AI agents use install_gui_driver to create or update resources in KiCAD-MCP-Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KiCAD-MCP-Server environment.

RISK

Why install_gui_driver is rated Medium

Installs a plugin into the user's KiCad environment, a reversible write operation.

From the tool's definition Deploy the in-KiCad GUI-driver helper plugin into the user

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs install_gui_driver 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 install_gui_driver, this is the rule to start with:

install_gui_driver Rate-limited

install_gui_driver stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "install_gui_driver": {
      "limits": [
        {
          "counter": "install_gui_driver_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect KiCAD-MCP-Server, apply this rule, and every install_gui_driver call is checked against it from then on.

FAQ

Questions about install_gui_driver

What does the install_gui_driver tool do? +

Deploy the in-KiCad GUI-driver helper plugin into the user. It is categorised as a Write tool in the KiCAD-MCP-Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on install_gui_driver? +

Register the KiCAD-MCP-Server MCP server in PolicyLayer and add a rule for install_gui_driver: 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.

What risk level is install_gui_driver? +

install_gui_driver is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit install_gui_driver? +

Yes. Add a rate_limit block to the install_gui_driver 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.

How do I block install_gui_driver completely? +

Set action: deny in the PolicyLayer policy for install_gui_driver. 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.

What MCP server provides install_gui_driver? +

install_gui_driver 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.

KEEP EXPLORING

More on KiCAD-MCP-Server, and thousands of servers like it.

This server

All 247 KiCAD-MCP-Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →