obj_run_process
A execute tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/obj-run-process.md
What obj_run_process does on Eda Agent
AI agents invoke obj_run_process 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 obj_run_process is rated High
Process execution is inherently an Execute category action. Given the tool's position in a comprehensive automation framework with persistent script bridge and design-plan executor capabilities, misuse could trigger uncontrolled operations affecting PCB/schematic designs.
From the tool's definition Tool name 'obj_run_process' indicates execution of processes. Within Altium Designer context (DelphiScript bridge for 290+ automation tools), process execution can trigger arbitrary design modifications, external commands, or side effects.
Attacks that exploit this kind of access
The rule that runs obj_run_process 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 obj_run_process, this is the rule to start with:
obj_run_process 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 obj_run_process call is checked against it from then on.
Questions about obj_run_process
obj_run_process 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 obj_run_process: 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.
obj_run_process 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 obj_run_process 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 obj_run_process. 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.
obj_run_process 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