proj_run_outjob_all
A execute tool on the Altium-MCP-Suite MCP server.
This record as markdown: /tools/altium-mcp-suite/proj-run-outjob-all.md
What proj_run_outjob_all does on Altium-MCP-Suite
AI agents invoke proj_run_outjob_all 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 proj_run_outjob_all is rated High
The tool executes output job generation/rendering operations across an entire project, which are external operations whose effects depend on project state and job configurations. This is Execute rather than Write because it triggers pre-configured automated processes rather than creating/modifying design data directly.
From the tool's definition Tool name 'proj_run_outjob_all' suggests running all output jobs in a project. The verb 'run' combined with 'outjob' (Altium Designer's output job configuration) indicates execution of external operations or build processes.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs proj_run_outjob_all 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 proj_run_outjob_all, this is the rule to start with:
proj_run_outjob_all 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 Altium-MCP-Suite, apply this rule, and every proj_run_outjob_all call is checked against it from then on.
Questions about proj_run_outjob_all
proj_run_outjob_all is a execute tool on the Altium-MCP-Suite MCP server. It is categorised as a Execute tool in the Altium-MCP-Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Altium-MCP-Suite MCP server in PolicyLayer and add a rule for proj_run_outjob_all: 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 Altium-MCP-Suite. Nothing to install.
proj_run_outjob_all 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_all 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_all. 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_all is provided by the Altium-MCP-Suite MCP server (M-R-Abedini/Altium-MCP-Suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Altium-MCP-Suite, and thousands of servers like it.
Across the catalogue