run_jobset · Kicad MCP: Risk & Policy

WHAT IT DOES

What run_jobset does on Kicad

AI agents invoke run_jobset to trigger actions in Kicad. 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 run_jobset needs a policy

The tool executes pre-defined automation workflows from jobset files, which can trigger various side effects including file generation, format conversions, and project modifications. While not directly destructive, the execution of arbitrary jobsets creates significant risk since jobset contents determine actual effects and could be weaponized to cause data loss, unauthorized exports, or system resource consumption.

From the tool's definition Tool name 'run_jobset' combined with description 'Run a KiCad jobset file' indicates execution of an external automation workflow.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_jobset Rate-limited

run_jobset 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": {
    "run_jobset": {
      "limits": [
        {
          "counter": "run_jobset_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 Kicad, so you can run agents against it safely.

FAQ

Questions about run_jobset

What does the run_jobset tool do? +

Run a KiCad jobset file. It is categorised as a Execute tool in the Kicad MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_jobset? +

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

What risk level is run_jobset? +

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

Can I rate-limit run_jobset? +

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

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

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