AI agents invoke run_ac_analysis to trigger actions in Spicelib. 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 circuit analysis—a computational operation with side effects determined by the simulation parameters (circuit definition, frequency range, etc.). While not destructive to data storage, it triggers external computation that could consume significant resources or be misused to DOS.
From the tool's definition Tool name 'run_ac_analysis' and server description indicate this runs AC analysis simulations. The description is empty, but the sibling tools (run_dc_op, run_sweep, run_transient) and server context confirm these are circuit simulation execution operations.
Documented attack patterns abuse exactly the kind of access run_ac_analysis gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Spicelib, and nothing reaches the server without passing your rules. This is the rule we recommend for run_ac_analysis:
{
"version": "1",
"default": "deny",
"tools": {
"run_ac_analysis": {
"limits": [
{
"counter": "run_ac_analysis_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_ac_analysis 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.
run_ac_analysis. It is categorised as a Execute tool in the Spicelib MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Spicelib MCP server in PolicyLayer and add a rule for run_ac_analysis: 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 Spicelib. Nothing to install.
run_ac_analysis 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 run_ac_analysis 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 run_ac_analysis. 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.
run_ac_analysis is provided by the Spicelib MCP server (lucasgerads/spicelib-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Spicelib, 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.
4 Spicelib tools catalogued and risk-classified — across an index of 43,000+ MCP servers.