proj_run_outjob
A execute tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/proj-run-outjob.md
What proj_run_outjob does on Eda Agent
AI agents invoke proj_run_outjob 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.
Why proj_run_outjob is rated High
Outjobs in Altium Designer trigger automated manufacturing output generation, design exports, and batch processing operations. Without explicit description, the name alone strongly suggests code/process execution rather than simple data retrieval. The blast radius is high: misconfigured outjob execution could generate incorrect manufacturing files, overwrite outputs, or trigger unintended batch operations.
From the tool's definition Tool name 'proj_run_outjob' combined with server context of 290+ automation tools for Altium Designer (schematic/PCB/library/project automation over DelphiScript bridge).
Attacks that exploit this kind of access
The rule that runs proj_run_outjob 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 proj_run_outjob, this is the rule to start with:
proj_run_outjob 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every proj_run_outjob call is checked against it from then on.
Questions about proj_run_outjob
proj_run_outjob 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.
Register the Eda Agent MCP server in PolicyLayer and add a rule for proj_run_outjob: 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.
proj_run_outjob is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the proj_run_outjob 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.
Set action: deny in the PolicyLayer policy for proj_run_outjob. 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.
proj_run_outjob 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.
More on Eda Agent, and thousands of servers like it.
Across the catalogue