// MCP TOOL REFERENCE

run_drc_check

ServerKiCad MCP Server
CategoryExecute

WHAT IT DOES

What run_drc_check does on KiCad MCP Server

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

THE RISK

High Risk

Why run_drc_check needs a policy

This tool triggers execution of KiCad's DRC engine on a specified project file. While DRC is a read-centric analysis (examining design rules), the tool executes an external operation with potential side effects depending on the project file provided. The operation is not a simple query but an active computation/check process. However, it does not create, modify, delete, or move data—it only reports analysis results.

From the tool's definition Tool name 'run_drc_check' and description 'Run a Design Rule Check on a KiCad PCB file' indicates execution of an external validation operation.

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

POLICY

How to control run_drc_check

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

policy.json

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

run_drc_check 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

Execute generate_pcb_thumbnail Generate a thumbnail image of a KiCad PCB layout using kicad-cli. Args: Execute generate_project_thumbnail Generate a thumbnail of a KiCad project's PCB layout (Alias for generate_pcb_thumbnail). Execute open_project Open a KiCad project in KiCad. Write export_bom_csv Export a Bill of Materials for a KiCad project. This tool attempts to gen Read analyze_bom Analyze a KiCad project's Bill of Materials. This tool will look for BOM Read analyze_project_circuit_patterns Identify circuit patterns in a KiCad project's schematic. Args: Read analyze_schematic_connections Analyze connections in a KiCad schematic. This tool provides detailed ana Read extract_project_netlist Extract netlist from a KiCad project's schematic. This tool finds the sch

All 16 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_check

What does the run_drc_check tool do? +

Run a Design Rule Check on a KiCad PCB file. Args: project_path: Path to the KiCad project file (.kicad_pro) ctx: MCP context for progress reporting Returns: Dictionary with DRC results and statistics. 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_check? +

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

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

Can I rate-limit run_drc_check? +

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

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

run_drc_check is provided by the KiCad MCP Server MCP server (lamaalrajih/kicad-mcp). 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 →

Free to start. No card required.

16 KiCad MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.