Check configured Workbench, Mechanical, MAPDL, and bridge paths.
AI agents call check_ansys_installation to retrieve information from Ansys Workbench without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and verifies the configuration of installed ANSYS components and their file system paths. It performs no mutations, does not execute simulations or external commands, and has no destructive capability. The blast radius of misuse is minimal—at worst, an agent learns what ANSYS paths are configured on the system, which is informational rather than harmful.
From the tool's definition The tool description states it 'Check[s] configured Workbench, Mechanical, MAPDL, and bridge paths.' This is a read-only operation that queries system configuration without modifying, executing arbitrary code, or causing destructive side effects.
Documented attack patterns abuse exactly the kind of access check_ansys_installation 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 check_ansys_installation:
{
"version": "1",
"default": "deny",
"tools": {
"check_ansys_installation": {}
}
}check_ansys_installation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check configured Workbench, Mechanical, MAPDL, and bridge paths. It is categorised as a Read tool in the Ansys Workbench MCP Server, which means it retrieves data without modifying state.
Register the Ansys Workbench MCP server in PolicyLayer and add a rule for check_ansys_installation: 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.
check_ansys_installation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_ansys_installation 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 check_ansys_installation. 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.
check_ansys_installation 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.