create_static_structural_system_live

THE RISK

Medium Risk

Why create_static_structural_system_live needs a policy

The tool creates a new simulation system within a running Ansys Workbench session. This is a Write operation — it creates/modifies data (a new analysis system) in the application. It does not delete data, execute arbitrary code, or involve financial transactions. Misuse could consume compute resources or corrupt a simulation project, but effects are generally reversible.

From the tool's definition "Create a Static Structural system in the running Workbench bridge"

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

POLICY

How to control create_static_structural_system_live

PolicyLayer is an MCP gateway — it sits between your AI agents and Ansys Workbench, and nothing reaches the server without passing your rules. This is the rule we recommend for create_static_structural_system_live:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_static_structural_system_live": {
      "limits": [
        {
          "counter": "create_static_structural_system_live_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_static_structural_system_live stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Ansys Workbench — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Ansys Workbench tools

Execute execute_workbench_script Execute Python/Workbench journal code inside the running Workbench bridge. Execute run_cfx_solver Run an Ansys CFX solver input file directly with cfx5solve.exe. Execute run_fluent_journal Run an Ansys Fluent journal directly with fluent.exe. Execute run_mapdl_input Run a Mechanical APDL input file with MAPDL. Execute run_workbench_journal Run an Ansys Workbench journal through RunWB2 as a direct batch job. Execute start_workbench_bridge Launch Workbench with the file-IPC bridge journal loaded. Execute stop_workbench_bridge Signal the Workbench bridge loop to stop. Execute create_and_run_thermal_bar_demo Create and solve a small steady thermal bar demo through direct Workbench batch.

All 29 Ansys Workbench tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_static_structural_system_live

What does the create_static_structural_system_live tool do? +

Create a Static Structural system in the running Workbench bridge. It is categorised as a Write tool in the Ansys Workbench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_static_structural_system_live? +

Register the Ansys Workbench MCP server in PolicyLayer and add a rule for create_static_structural_system_live: 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 Ansys Workbench. Nothing to install.

What risk level is create_static_structural_system_live? +

create_static_structural_system_live is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_static_structural_system_live? +

Yes. Add a rate_limit block to the create_static_structural_system_live 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 create_static_structural_system_live completely? +

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

create_static_structural_system_live is provided by the Ansys Workbench MCP server (hongwenwang36-eng/ansys-workbench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ansys Workbench tool call.

Start from Ansys Workbench, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →