proj_run_output

A execute tool on the Eda Agent MCP server.

SERVEREda Agent SOURCEsalitronic/eda-agent

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eda-agent/proj-run-output.md

WHAT IT DOES

What proj_run_output does on Eda Agent

AI agents invoke proj_run_output 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.

RISK

Why proj_run_output is rated High

The tool description is empty, which lowers confidence slightly, but the name 'run_output' combined with the server's role as an automation bridge over DelphiScript strongly indicates this executes external operations (design compilation, artifact generation, or fabrication file production). These have side effects dependent on arguments and cannot always be easily reversed.

From the tool's definition Tool name 'proj_run_output' suggests execution of a project output operation. Given the server context (Altium Designer automation with 290+ tools for design/PCB workflows), 'run_output' likely triggers code generation, file exports, or design rule checks…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proj_run_output 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_output, this is the rule to start with:

proj_run_output Rate-limited

proj_run_output 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": {
    "proj_run_output": {
      "limits": [
        {
          "counter": "proj_run_output_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every proj_run_output call is checked against it from then on.

FAQ

Questions about proj_run_output

What does the proj_run_output tool do? +

proj_run_output 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.

How do I enforce a policy on proj_run_output? +

Register the Eda Agent MCP server in PolicyLayer and add a rule for proj_run_output: 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.

What risk level is proj_run_output? +

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

Can I rate-limit proj_run_output? +

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

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

proj_run_output 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.

KEEP EXPLORING

More on Eda Agent, and thousands of servers like it.

This server

All 345 Eda Agent tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →