kicad.run_erc · Eda MCP: Risk & Policy

WHAT IT DOES

What kicad.run_erc does on Eda

AI agents invoke kicad.run_erc 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_erc needs a policy

ERC (Electrical Rules Check) is a standard KiCad operation that runs a validation/analysis pass over the schematic. The 'run_' prefix indicates execution of an automated check. It reads design data and produces a report but does not modify data, so it is Execute rather than Write or Read. Description is empty, lowering confidence. No financial or destructive implications expected.

From the tool's definition Tool name: kicad.run_erc — the 'run_' prefix strongly suggests executing a process (Electrical Rules Check in KiCad EDA context).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kicad.run_erc Rate-limited

kicad.run_erc 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_erc": {
      "limits": [
        {
          "counter": "kicad.run_erc_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_erc

What does the kicad.run_erc tool do? +

kicad.run_erc. 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_erc? +

Register the Eda MCP server in PolicyLayer and add a rule for kicad.run_erc: 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_erc? +

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

Can I rate-limit kicad.run_erc? +

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

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

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