Check Terminal API connectivity.
AI agents call health_check to retrieve information from Umbrella Terminal MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a status/connectivity check that only reads and reports the current state of the API. It has no side effects, does not modify data, and does not execute code or perform destructive operations. The blast radius is minimal—failure to access the tool or false connectivity status would only affect downstream queries, not cause data loss or unauthorized actions.
From the tool's definition Tool name 'health_check' and description 'Check Terminal API connectivity' indicate a diagnostic query that retrieves status information without modifying any data or triggering external operations.
Attacks that exploit this kind of access
Check Terminal API connectivity. It is categorised as a Read tool in the Umbrella Terminal MCP MCP Server, which means it retrieves data without modifying state.
Register the Umbrella Terminal MCP server in PolicyLayer and add a rule for health_check: 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 Umbrella Terminal MCP. Nothing to install.
health_check 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 health_check 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 health_check. 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.
health_check is provided by the Umbrella Terminal MCP server (theblackcompany/umbrella_terminal_mcp). 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 →