kicad_run_drc

GUI playbook: open the Design Rules Checker dialog, click

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

High RISK CLASS

Category Execute

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/kicad-run-drc.md

WHAT IT DOES

What kicad_run_drc does on KiCAD-MCP-Server

AI agents invoke kicad_run_drc 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.

RISK

Why kicad_run_drc is rated High

Executes design validation checks; result-dependent behavior with no permanent data modification.

From the tool's definition run_drc, Design Rules Checker dialog, click

Attacks that exploit this kind of access

RECOMMENDED RULE

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

kicad_run_drc Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kicad_run_drc": {
      "limits": [
        {
          "counter": "kicad_run_drc_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 kicad_run_drc call is checked against it from then on.

FAQ

Questions about kicad_run_drc

What does the kicad_run_drc tool do? +

GUI playbook: open the Design Rules Checker dialog, click. 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.

How do I enforce a policy on kicad_run_drc? +

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

kicad_run_drc is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit kicad_run_drc? +

Yes. Add a rate_limit block to the kicad_run_drc 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 kicad_run_drc completely? +

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

kicad_run_drc 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 → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →