New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

run_drc

Run the KiCAD Design Rule Check (DRC) on the current PCB and return violations. Optionally save the report to a file.

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/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"

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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of KiCAD-MCP-Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.