kicad.run_drc · Eda MCP: Risk & Policy

WHAT IT DOES

What kicad.run_drc does on Eda

AI agents invoke kicad.run_drc to trigger actions in Eda. 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 IT NEEDS A POLICY

Why kicad.run_drc needs a policy

The tool name 'run_drc' strongly implies executing a Design Rule Check (DRC), which is a read/analysis operation that scans the PCB design for rule violations. The 'run' prefix places it in the Execute category. A DRC typically only reads the design and produces a report without modifying data, but since the description is empty, there is some uncertainty about side effects.

From the tool's definition Tool name: kicad.run_drc — 'run' prefix suggests execution of a process (Design Rule Check)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kicad.run_drc Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kicad.run_drc": {
      "limits": [
        {
          "counter": "kicad.run_drc_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Eda, so you can run agents against it safely.

FAQ

Questions about kicad.run_drc

What does the kicad.run_drc tool do? +

kicad.run_drc. It is categorised as a Execute tool in the Eda MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on kicad.run_drc? +

Register the Eda MCP server in PolicyLayer and add a rule for kicad.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. Nothing to install.

What risk level is kicad.run_drc? +

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

Can I rate-limit kicad.run_drc? +

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

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

kicad.run_drc is provided by the Eda MCP server (saeronlab/eda-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.