run_drc

THE RISK

High Risk

Why run_drc needs a policy

The tool executes a DRC analysis process on the current PCB design and can write a report file to disk. The primary action is triggering an external operation (running DRC) whose effects depend on the current board state, placing it in the Execute category. The optional file save adds a minor Write side effect.

From the tool's definition "Run the KiCAD Design Rule Check (DRC)" and "Optionally save the report to a file"

Documented attack patterns abuse exactly the kind of access run_drc gives an agent:

POLICY

How to control run_drc

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 run_drc:

policy.json

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

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.

Create a free account and register KiCAD-MCP-Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More KiCAD-MCP-Server tools

Destructive delete_component Remove a component from the PCB by its reference designator. Destructive delete_schematic_component Remove a placed symbol from a KiCAD schematic (.kicad_sch). This removes the symbol insta Destructive delete_schematic_net_label Remove a net label from the schematic. Destructive delete_schematic_wire Remove a wire from the schematic by start and end coordinates. Destructive delete_symbol Remove a symbol from a .kicad_sym library file. Destructive delete_trace Delete traces from the PCB. Can delete by UUID, position, or bulk-delete all traces on a n Destructive remove_schematic_component_property Remove a single custom property from a placed schematic symbol. Built-in fields (Referenc Execute autoroute Run Freerouting autorouter on the current PCB. Exports to Specctra DSN, runs Freerouting C

All 157 KiCAD-MCP-Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in KiCAD-MCP-Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about run_drc

What does the run_drc tool do? +

Run the KiCAD Design Rule Check (DRC) on the current PCB and return violations. Optionally save the report to a 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.

How do I enforce a policy on run_drc? +

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

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

Can I rate-limit run_drc? +

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

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

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.

Enforce policy on every KiCAD-MCP-Server tool call.

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.

CHECK YOUR STACK →