This record as markdown: /tools/eda-agent/pcb-run-drc.md
What pcb_run_drc does on Eda Agent
AI agents invoke pcb_run_drc to trigger actions in Eda Agent. 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 pcb_run_drc is rated High
DRC (Design Rule Check) is an automated analysis operation that processes design data and may modify internal state (e.g., violation flags, annotations). While DRC itself is typically non-destructive and read-heavy, it executes procedural logic within the design environment and can trigger downstream actions.
From the tool's definition pcb_run_drc runs Design Rule Check operations, which execute validation logic over the active PCB design. The tool name indicates procedural execution; the sibling tools (app_attach, app_create_document, app_get_active_document) show this server controls…
Attacks that exploit this kind of access
The rule that runs pcb_run_drc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Eda Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pcb_run_drc, this is the rule to start with:
pcb_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 Eda Agent, apply this rule, and every pcb_run_drc call is checked against it from then on.
Questions about pcb_run_drc
pcb_run_drc is a execute tool on the Eda Agent MCP server. It is categorised as a Execute tool in the Eda Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Eda Agent MCP server in PolicyLayer and add a rule for pcb_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 Eda Agent. Nothing to install.
pcb_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 pcb_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 pcb_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.
pcb_run_drc is provided by the Eda Agent MCP server (salitronic/eda-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Eda Agent, and thousands of servers like it.
Across the catalogue