execute_workbench_script

THE RISK

High Risk

Why execute_workbench_script needs a policy

This tool directly executes arbitrary code within the Ansys Workbench environment, which can trigger external operations, modify simulations, access file systems, and generate results whose effects depend entirely on the injected code arguments.

From the tool's definition Tool description explicitly states it executes 'Python/Workbench journal code' with arbitrary script content capability. The method accepts custom code execution without apparent input sanitization constraints.

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

POLICY

How to control execute_workbench_script

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_workbench_script": {
      "limits": [
        {
          "counter": "execute_workbench_script_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

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.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Ansys Workbench tools

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. Execute create_cfx_flow_system_live Create a Fluid Flow (CFX) system in the running Workbench bridge.

All 29 Ansys Workbench tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Ansys Workbench → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about execute_workbench_script

What does the execute_workbench_script tool do? +

Execute Python/Workbench journal code inside the running Workbench bridge. It is categorised as a Execute tool in the Ansys Workbench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_workbench_script? +

Register the Ansys Workbench MCP server in PolicyLayer and add a rule for execute_workbench_script: 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 execute_workbench_script? +

execute_workbench_script is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_workbench_script? +

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

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

execute_workbench_script 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 →