Set whether schematic UI opens reuse a single live schematic path.
AI agents use setSchematicUiSingleWindow to create or update resources in Ltspice — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ltspice environment.
This tool configures application settings that control UI behavior and state management. While it does not create, delete, or execute code, it modifies persistent application configuration/preferences. This is a Write operation (reversible configuration change) rather than Read (it actively changes state) or Execute (it does not run arbitrary code or commands).
From the tool's definition 'Set whether schematic UI opens reuse a single live schematic path' — modifies UI state/preferences for LTspice application behavior; changes how the application handles window management and file paths.
Documented attack patterns abuse exactly the kind of access setSchematicUiSingleWindow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ltspice, and nothing reaches the server without passing your rules. This is the rule we recommend for setSchematicUiSingleWindow:
{
"version": "1",
"default": "deny",
"tools": {
"setSchematicUiSingleWindow": {
"limits": [
{
"counter": "setschematicuisinglewindow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setSchematicUiSingleWindow stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set whether schematic UI opens reuse a single live schematic path. It is categorised as a Write tool in the Ltspice MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ltspice MCP server in PolicyLayer and add a rule for setSchematicUiSingleWindow: 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 Ltspice. Nothing to install.
setSchematicUiSingleWindow 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 setSchematicUiSingleWindow 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 setSchematicUiSingleWindow. 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.
setSchematicUiSingleWindow is provided by the Ltspice MCP server (xuio/ltspice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ltspice, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
71 Ltspice tools catalogued and risk-classified — across an index of 43,000+ MCP servers.