pcb_get_nets
Get all unique net names from the active PCB board.
This record as markdown: /tools/eda-agent/pcb-get-nets.md
What pcb_get_nets does on Eda Agent
AI agents call pcb_get_nets to retrieve information from Eda Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pcb_get_nets is rated Low
The tool only retrieves information about existing nets in the PCB design. It has no side effects, does not modify design state, and poses no risk of data loss or unintended operations. Misuse would at worst expose the net topology, which is design information already visible in the active document.
From the tool's definition Tool retrieves 'all unique net names from the active PCB board' with no modification, deletion, or execution capability described. This is a data query operation similar to 'list' or 'get'.
Attacks that exploit this kind of access
The rule that runs pcb_get_nets 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_get_nets, this is the rule to start with:
pcb_get_nets is read-only, so it stays allowed. 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_get_nets call is checked against it from then on.
Questions about pcb_get_nets
Get all unique net names from the active PCB board. It is categorised as a Read tool in the Eda Agent MCP Server, which means it retrieves data without modifying state.
Register the Eda Agent MCP server in PolicyLayer and add a rule for pcb_get_nets: 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_get_nets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pcb_get_nets 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_get_nets. 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_get_nets 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.
This server
Across the catalogue