Create a Workbench Steady-State Thermal system using a direct batch journal.
AI agents invoke create_steady_state_thermal_system to trigger actions in Ansys Workbench. 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 batch journal script within Ansys Workbench to instantiate a Steady-State Thermal simulation system. It goes beyond a simple write operation because it actively runs scripted automation (batch processing) that triggers external application behavior.
From the tool's definition 'Create a Workbench Steady-State Thermal system using a direct batch journal' — triggers execution of a scripted batch journal in Ansys Workbench to create and configure a simulation system
Documented attack patterns abuse exactly the kind of access create_steady_state_thermal_system gives an agent:
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_steady_state_thermal_system:
{
"version": "1",
"default": "deny",
"tools": {
"create_steady_state_thermal_system": {
"limits": [
{
"counter": "create_steady_state_thermal_system_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}create_steady_state_thermal_system 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.
Create a Workbench Steady-State Thermal system using a direct batch journal. 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.
Register the Ansys Workbench MCP server in PolicyLayer and add a rule for create_steady_state_thermal_system: 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.
create_steady_state_thermal_system 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 create_steady_state_thermal_system 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 create_steady_state_thermal_system. 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.
create_steady_state_thermal_system 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.
Start from Ansys Workbench, 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.
29 Ansys Workbench tools catalogued and risk-classified — across an index of 43,000+ MCP servers.