Check whether the Workbench bridge journal is running and responding.
AI agents call check_workbench_connection 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 is a health-check or status-verification tool. It queries the state of a running service (the Workbench bridge journal) and returns a response. No side effects, no data modification, no code execution triggered by the check itself. This is purely informational, making it a Read operation with low severity and high confidence.
From the tool's definition Tool name 'check_workbench_connection' and description 'Check whether the Workbench bridge journal is running and responding' indicate a diagnostic query operation that only retrieves status information without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access check_workbench_connection 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_workbench_connection:
{
"version": "1",
"default": "deny",
"tools": {
"check_workbench_connection": {}
}
}check_workbench_connection 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 whether the Workbench bridge journal is running and responding. 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_workbench_connection: 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_workbench_connection 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_workbench_connection 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_workbench_connection. 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_workbench_connection 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.