Close the LTspice window associated with a render session.
AI agents call endLtspiceRenderSession to permanently remove resources in Ltspice — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Closing a window/session is an irreversible termination action — any unsaved simulation state or render session data associated with that window would be lost. While it doesn't delete files on disk, it forcibly ends a session in a way that cannot be undone, placing it closer to Destructive than a simple Write or Execute.
From the tool's definition Close the LTspice window associated with a render session
Documented attack patterns abuse exactly the kind of access endLtspiceRenderSession 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 endLtspiceRenderSession:
{
"version": "1",
"default": "deny",
"hide": [
"endLtspiceRenderSession"
]
}endLtspiceRenderSession disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Close the LTspice window associated with a render session. It is categorised as a Destructive tool in the Ltspice MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ltspice MCP server in PolicyLayer and add a rule for endLtspiceRenderSession: 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.
endLtspiceRenderSession is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the endLtspiceRenderSession 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 endLtspiceRenderSession. 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.
endLtspiceRenderSession 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.