pcb_plan_placement
A execute tool on the Eda Agent MCP server.
This record as markdown: /tools/eda-agent/pcb-plan-placement.md
What pcb_plan_placement does on Eda Agent
AI agents invoke pcb_plan_placement 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_plan_placement is rated High
The tool name suggests it plans or executes PCB component placement. Given the server description mentions 'connectivity-driven auto-placement' and 'autonomous design-plan executor', this likely triggers an automated placement operation that modifies the PCB layout. This falls under Execute (or Write at minimum) as it performs design automation. The description is empty, reducing confidence.
From the tool's definition Tool name 'pcb_plan_placement' on a server that advertises 'connectivity-driven auto-placement' and 'autonomous design-plan executor' capabilities.
Attacks that exploit this kind of access
The rule that runs pcb_plan_placement 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_plan_placement, this is the rule to start with:
pcb_plan_placement 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_plan_placement call is checked against it from then on.
Questions about pcb_plan_placement
pcb_plan_placement 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_plan_placement: 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_plan_placement 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_plan_placement 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_plan_placement. 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_plan_placement 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