AI agents invoke run_mapdl_input 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 arbitrary MAPDL scripts whose effects depend entirely on the contents of the input file argument. MAPDL input files can perform complex simulations, modify geometry, alter material properties, and trigger solver operations.
From the tool's definition Tool name 'run_mapdl_input' indicates execution of MAPDL (Mechanical APDL) input files. MAPDL is a scripting language for the Ansys finite element solver that can execute arbitrary computational commands, modify simulation models, and trigger external…
Documented attack patterns abuse exactly the kind of access run_mapdl_input 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 run_mapdl_input:
{
"version": "1",
"default": "deny",
"tools": {
"run_mapdl_input": {
"limits": [
{
"counter": "run_mapdl_input_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_mapdl_input 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 a Mechanical APDL input file with MAPDL. 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 run_mapdl_input: 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.
run_mapdl_input 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 run_mapdl_input 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 run_mapdl_input. 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.
run_mapdl_input 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.