pcb_build_from_project
A execute tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/pcb-build-from-project.md
What pcb_build_from_project does on Eda Agent
AI agents invoke pcb_build_from_project 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 pcb_build_from_project is rated High
This tool executes an automated PCB build workflow triggered by project parameters, which is an external design operation with effects dependent on the project state and configuration. While not destructive by itself, it runs code/scripts (DelphiScript) whose side effects on the PCB design depend on input arguments, making it Execute rather than Write.
From the tool's definition Tool name 'pcb_build_from_project' combined with server context showing 290+ tools for 'schematic, PCB, library & project automation' and 'persistent DelphiScript bridge' indicates execution of design operations.
Attacks that exploit this kind of access
The rule that runs pcb_build_from_project 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 pcb_build_from_project, this is the rule to start with:
pcb_build_from_project 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 pcb_build_from_project call is checked against it from then on.
Questions about pcb_build_from_project
pcb_build_from_project 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 pcb_build_from_project: 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.
pcb_build_from_project 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 pcb_build_from_project 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 pcb_build_from_project. 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.
pcb_build_from_project 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