Create an LTspice .asc schematic from a SPICE netlist using auto-placement/routing.
AI agents use createSchematicFromNetlist 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 a new file (LTspice schematic) from input data (a SPICE netlist). This is a Write operation because it generates new data artifacts that persist but are reversible. Severity is medium because misuse could create malformed or unintended circuit designs, but the effect is limited to file creation without executing simulations or modifying existing critical designs.
From the tool's definition Tool description states it will 'Create an LTspice .asc schematic from a SPICE netlist', using language indicating creation of a new file artifact ('Create'). The operation is reversible—the generated schematic file can be modified or deleted.
Documented attack patterns abuse exactly the kind of access createSchematicFromNetlist 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 createSchematicFromNetlist:
{
"version": "1",
"default": "deny",
"tools": {
"createSchematicFromNetlist": {
"limits": [
{
"counter": "createschematicfromnetlist_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createSchematicFromNetlist 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 an LTspice .asc schematic from a SPICE netlist using auto-placement/routing. 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 createSchematicFromNetlist: 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.
createSchematicFromNetlist 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 createSchematicFromNetlist 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 createSchematicFromNetlist. 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.
createSchematicFromNetlist 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.