Simulate the loaded electrical circuit and return the waveform as a VIEWABLE PNG, so you (the host model) can SEE the response and do circuit design in the loop: edit the netlist (ops circuit_import) → simulate → look at the curve → fix. Import a SPICE/KiCad/EPLAN design first via ops verb circui...
AI agents use circuit_plot to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Analysis: "tran" (time), "ac" (Bode), "dc" (sweep). Default transient. |
machine | string | — | Target cell: "local", "primary", or a deviceId / alias. Default "local". |
signals | array | — | Optional signal names to plot, e.g. ["V(out)"]. Default: all node traces. |
Parameters from the server's own tool schema.
An AI agent can call circuit_plot faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Simulate the loaded electrical circuit and return the waveform as a VIEWABLE PNG, so you (the host model) can SEE the response and do circuit design in the loop: edit the netlist (ops circuit_import) → simulate → look at the curve → fix. Import a SPICE/KiCad/EPLAN design first via ops verb circuit_import. Picks the analysis from type (op→transient, tran, ac for a Bode plot, dc sweep); signals filters which node traces to draw. For raw numbers instead of a picture use ops verbs circuit_simulate / circuit_measure / circuit_erc. Targets any mesh device via machine. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
circuit_plot accepts 3 parameters: type, machine, signals. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for circuit_plot: 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 Yaver. Nothing to install.
circuit_plot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the circuit_plot 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 circuit_plot. 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.
circuit_plot is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.