runVerificationPlan
AI agents invoke runVerificationPlan 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 verification operations (a form of test execution), which aligns with the Execute category. It is not a simple Read operation because verification plans inherently trigger simulations or tests with observable side effects. It is not Destructive because verification typically does not irreversibly delete data.
From the tool's definition Tool name 'runVerificationPlan' combined with server description stating the MCP server enables 'verification' via 'natural language or agents.' A verification plan in circuit simulation typically involves executing test sequences, assertions, or automated…
Documented attack patterns abuse exactly the kind of access runVerificationPlan 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 runVerificationPlan:
{
"version": "1",
"default": "deny",
"tools": {
"runVerificationPlan": {
"limits": [
{
"counter": "runverificationplan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}runVerificationPlan 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.
runVerificationPlan. 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 runVerificationPlan: 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.
runVerificationPlan 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 runVerificationPlan 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 runVerificationPlan. 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.
runVerificationPlan 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.