run_output_jobs

What run_output_jobs does on Altium-MCP-Suite

AI agents invoke run_output_jobs to trigger actions in Altium-MCP-Suite. 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 run_output_jobs is rated High

This tool executes output job containers in Altium, which generates design outputs (Gerber files, PDFs, BOMs, etc.). The effects are dependent on what jobs are specified and their configuration—an AI agent could generate incorrect manufacturing files or documentation. While not immediately destructive or financial, execution of unvalidated jobs poses significant risk to design integrity and manufacturing accuracy.

From the tool's definition Tool name is 'run_output_jobs' with description 'Run specified output job containers'. The verb 'run' indicates execution of jobs, which are computational operations whose effects depend on job configuration and content.

The rule that runs run_output_jobs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Altium-MCP-Suite, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_output_jobs, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_output_jobs": {
      "limits": [
        {
          "counter": "run_output_jobs_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about run_output_jobs