run_drc
Run the KiCAD Design Rule Check (DRC) on the current PCB and return violations. Optionally save the report to a file.
This record as markdown: /tools/mixelpixx-kicad-mcp-server/run-drc.md
What run_drc does on KiCAD-MCP-Server
AI agents invoke 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.
Why run_drc is rated High
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"
Attacks that exploit this kind of access
The rule that runs 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 run_drc, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect KiCAD-MCP-Server, apply this rule, and every run_drc call is checked against it from then on.
Questions about run_drc
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.
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.
run_drc 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 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.
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.
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.
More on KiCAD-MCP-Server, and thousands of servers like it.
Across the catalogue