kicad_run_spice

A execute tool on the Eda Agent MCP server.

SERVEREda Agent SOURCEsalitronic/eda-agent

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/eda-agent/kicad-run-spice.md

WHAT IT DOES

What kicad_run_spice does on Eda Agent

AI agents invoke kicad_run_spice 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.

RISK

Why kicad_run_spice is rated High

Runs SPICE simulations; arbitrary circuit parameters could cause resource exhaustion or unintended computations.

From the tool's definition uninformative description; kicad_run_spice suggests circuit simulation execution

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs kicad_run_spice 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 kicad_run_spice, this is the rule to start with:

kicad_run_spice Rate-limited

kicad_run_spice 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_spice": {
      "limits": [
        {
          "counter": "kicad_run_spice_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every kicad_run_spice call is checked against it from then on.

FAQ

Questions about kicad_run_spice

What does the kicad_run_spice tool do? +

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

How do I enforce a policy on kicad_run_spice? +

Register the Eda Agent MCP server in PolicyLayer and add a rule for kicad_run_spice: 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.

What risk level is kicad_run_spice? +

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

Can I rate-limit kicad_run_spice? +

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

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

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

KEEP EXPLORING

More on Eda Agent, and thousands of servers like it.

This server

All 726 Eda Agent tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →