Get LTspice symbol library ZIP status and basic counts.
AI agents call getLtspiceLibraryStatus to retrieve information from Ltspice without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to fetch the status of a library and retrieve count metrics. It has no side effects, does not execute code, does not modify data, and does not delete or move anything. It aligns with the 'Read' category as defined: retrieves or queries data with no side effects.
From the tool's definition Tool description states "Get LTspice symbol library ZIP status and basic counts" — a query operation that retrieves status information and metrics without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access getLtspiceLibraryStatus 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 getLtspiceLibraryStatus:
{
"version": "1",
"default": "deny",
"tools": {
"getLtspiceLibraryStatus": {}
}
}getLtspiceLibraryStatus is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get LTspice symbol library ZIP status and basic counts. It is categorised as a Read tool in the Ltspice MCP Server, which means it retrieves data without modifying state.
Register the Ltspice MCP server in PolicyLayer and add a rule for getLtspiceLibraryStatus: 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.
getLtspiceLibraryStatus is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getLtspiceLibraryStatus 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 getLtspiceLibraryStatus. 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.
getLtspiceLibraryStatus 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.