Check whether the SSH ControlMaster session to the HPC cluster is alive.
AI agents call check_connection to retrieve information from Tacc Mcp Bio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a diagnostic/status check tool that queries the state of an existing connection. It has no side effects, does not execute code, does not modify data, and does not delete anything. It falls squarely into the Read category as the least risky operation. Severity is low because a successful or failed check cannot cause harm to the HPC cluster or data.
From the tool's definition The tool 'check_connection' checks the status of an SSH session without modifying, executing, or destroying anything. The description explicitly states it only verifies whether a connection 'is alive'.
Attacks that exploit this kind of access
Check whether the SSH ControlMaster session to the HPC cluster is alive. It is categorised as a Read tool in the Tacc Mcp Bio MCP Server, which means it retrieves data without modifying state.
Register the Tacc Mcp Bio MCP server in PolicyLayer and add a rule for check_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 Tacc Mcp Bio. Nothing to install.
check_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_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_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_connection is provided by the Tacc Mcp Bio MCP server (narasimhan-lab/tacc-mcp-bio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →