List all component instances in a cellview.
AI agents call virtuoso_get_instances 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 component instance information from a Cadence Virtuoso schematic without creating, modifying, or deleting any design data. It is a read-only inspection operation with no side effects, fitting the Read category. The severity is low as misuse would only expose design information rather than cause harm to the schematic or system.
From the tool's definition Tool name 'virtuoso_get_instances' and description 'List all component instances in a cellview' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
List all component instances in a cellview. 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 virtuoso_get_instances: 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.
virtuoso_get_instances 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 virtuoso_get_instances 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 virtuoso_get_instances. 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.
virtuoso_get_instances 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 →