Get a list of all nets in a schematic and their connected terminals/pins.
AI agents call get_nets to retrieve information from Virtuoso Schematic MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about nets and their connections in a Cadence Virtuoso schematic. It performs only inspection and data retrieval without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal since it only exposes existing design information without the ability to alter the schematic.
From the tool's definition Tool name 'get_nets' and description 'Get a list of all nets in a schematic and their connected terminals/pins' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get a list of all nets in a schematic and their connected terminals/pins. It is categorised as a Read tool in the Virtuoso Schematic MCP MCP Server, which means it retrieves data without modifying state.
Register the Virtuoso Schematic MCP server in PolicyLayer and add a rule for 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 Virtuoso Schematic MCP. Nothing to install.
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 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 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.
get_nets is provided by the Virtuoso Schematic MCP server (michelebergo/virtuoso-schematic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →