Run LTspice batch simulation for an existing schematic (.asc) file.
AI agents invoke simulateSchematicFile to trigger actions in Ltspice. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes LTspice simulations on provided schematic files. While not destructive (simulations do not modify persistent state), the tool triggers external code execution whose outcomes depend on schematic parameters—a hallmark of Execute category.
From the tool's definition Tool description states 'Run LTspice batch simulation' which triggers external simulation software execution.
Documented attack patterns abuse exactly the kind of access simulateSchematicFile 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 simulateSchematicFile:
{
"version": "1",
"default": "deny",
"tools": {
"simulateSchematicFile": {
"limits": [
{
"counter": "simulateschematicfile_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}simulateSchematicFile stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run LTspice batch simulation for an existing schematic (.asc) file. It is categorised as a Execute tool in the Ltspice MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ltspice MCP server in PolicyLayer and add a rule for simulateSchematicFile: 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.
simulateSchematicFile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the simulateSchematicFile 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 simulateSchematicFile. 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.
simulateSchematicFile 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.