List archived (terminal) queue jobs retained across daemon restarts.
AI agents call listJobHistory 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 retrieves and displays archived job history data from the LTspice daemon. It performs a query operation to show past queue jobs without modifying, deleting, or executing any operations.
From the tool's definition Tool name is 'listJobHistory' and description states 'List archived (terminal) queue jobs retained across daemon restarts.' The verb 'list' and action of retrieving/querying historical job data indicates read-only access with no side effects.
Documented attack patterns abuse exactly the kind of access listJobHistory 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 listJobHistory:
{
"version": "1",
"default": "deny",
"tools": {
"listJobHistory": {}
}
}listJobHistory 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.
List archived (terminal) queue jobs retained across daemon restarts. 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 listJobHistory: 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.
listJobHistory 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 listJobHistory 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 listJobHistory. 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.
listJobHistory 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.