Critical Risk →

hfss_delete_variable

Delete a design variable

How to control hfss_delete_variable ↓

What hfss_delete_variable does on HFSS MCP Server

AI agents call hfss_delete_variable to permanently remove resources in HFSS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why hfss_delete_variable needs a policy

The tool performs an irreversible deletion of design variables in an ANSYS HFSS simulation project. Deleting variables cannot be undone and could break dependent model parameters, simulations, or analyses. While the blast radius is somewhat scoped to a single design project rather than system-wide data, the action is fundamentally destructive and warrants the highest severity short of critical.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a design variable'. This is an irreversible operation that removes data from the HFSS design.

Documented attack patterns abuse exactly the kind of access hfss_delete_variable gives an agent:

How to control hfss_delete_variable

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_delete_variable:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "hfss_delete_variable"
  ]
}

hfss_delete_variable disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register HFSS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about hfss_delete_variable

What does the hfss_delete_variable tool do? +

Delete a design variable. It is categorised as a Destructive tool in the HFSS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on hfss_delete_variable? +

Register the HFSS MCP Server MCP server in PolicyLayer and add a rule for hfss_delete_variable: 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.

What risk level is hfss_delete_variable? +

hfss_delete_variable is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit hfss_delete_variable? +

Yes. Add a rate_limit block to the hfss_delete_variable 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.

How do I block hfss_delete_variable completely? +

Set action: deny in the PolicyLayer policy for hfss_delete_variable. 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.

What MCP server provides hfss_delete_variable? +

hfss_delete_variable 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.

Enforce policy on every HFSS MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.