AI agents invoke hfss_run_analysis to trigger actions in HFSS MCP Server. 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 a simulation—an external operation with effects that depend on arguments (project setup, analysis configuration). It is not a simple read (no data retrieval only), not a write (does not create/modify persistent design artifacts), not destructive (simulation results do not irreversibly delete data), and not financial.
From the tool's definition Tool name 'hfss_run_analysis' and description 'Run simulation analysis' indicate execution of external computational operations.
Documented attack patterns abuse exactly the kind of access hfss_run_analysis gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HFSS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for hfss_run_analysis:
{
"version": "1",
"default": "deny",
"tools": {
"hfss_run_analysis": {
"limits": [
{
"counter": "hfss_run_analysis_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}hfss_run_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 simulation analysis. It is categorised as a Execute tool in the HFSS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the HFSS MCP Server MCP server in PolicyLayer and add a rule for hfss_run_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 HFSS MCP Server. Nothing to install.
hfss_run_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 hfss_run_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 hfss_run_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.
hfss_run_analysis is provided by the HFSS MCP Server MCP server (leonardwy/hfss_mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HFSS MCP Server, 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.
28 HFSS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.