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

get_drc_violations

Return the list of current DRC violations on the PCB, optionally filtered by severity (error, warning).

SERVERKiCAD-MCP-Server SOURCEmixelpixx/kicad-mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mixelpixx-kicad-mcp-server/get-drc-violations.md

What get_drc_violations does on KiCAD-MCP-Server

AI agents call get_drc_violations to retrieve information from KiCAD-MCP-Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_drc_violations is rated Low

This tool queries and retrieves existing DRC violation data from the PCB design without modifying, executing operations, or deleting anything. It is a pure read operation that returns diagnostic information, optionally filtered by severity level. No state changes occur on the board or design when called.

From the tool's definition Tool name and description: 'get_drc_violations' with 'Return the list of current DRC violations on the PCB'. The verb 'Return' and 'list' indicate data retrieval with no side effects. DRC (Design Rule Check) violations are read-only diagnostic information.

Questions about get_drc_violations

What does the get_drc_violations tool do? +

Return the list of current DRC violations on the PCB, optionally filtered by severity (error, warning). It is categorised as a Read tool in the KiCAD-MCP-Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_drc_violations? +

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

get_drc_violations is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_drc_violations? +

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

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

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