Create a circuit from high-level intent templates (filters, amplifier, regulator).
AI agents use createIntentCircuit 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 creates or generates new circuit designs, which constitutes data creation and modification—a Write operation. While the created circuits could be used to simulate designs that might have real-world implications, the tool itself only generates reversible schematic artifacts.
From the tool's definition The tool name is 'createIntentCircuit' and the description states it will 'Create a circuit from high-level intent templates'. This involves creating new schematic data that is stored and reversible (can be modified or deleted later).
Documented attack patterns abuse exactly the kind of access createIntentCircuit 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 createIntentCircuit:
{
"version": "1",
"default": "deny",
"tools": {
"createIntentCircuit": {
"limits": [
{
"counter": "createintentcircuit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createIntentCircuit 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.
Create a circuit from high-level intent templates (filters, amplifier, regulator). 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 createIntentCircuit: 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.
createIntentCircuit 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 createIntentCircuit 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 createIntentCircuit. 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.
createIntentCircuit 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.