Server liveness probe (free). Returns {ok, network}. No item counts exposed.
AI agents call get_health to retrieve information from Wellness Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a basic health/liveness probe that queries server status and returns operational state information. It performs no modifications, executions, deletions, or financial operations. The explicit statement that no sensitive data (item counts) is exposed and that it is free further confirms it is a safe read operation with minimal blast radius if misused.
From the tool's definition Tool name 'get_health' and description 'Server liveness probe (free). Returns {ok, network}. No item counts exposed.' indicates a simple status check that retrieves read-only health information with no side effects.
Attacks that exploit this kind of access
Server liveness probe (free). Returns {ok, network}. No item counts exposed. It is categorised as a Read tool in the Wellness Manager MCP Server, which means it retrieves data without modifying state.
Register the Wellness Manager MCP server in PolicyLayer and add a rule for get_health: 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 Wellness Manager. Nothing to install.
get_health 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 get_health 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 get_health. 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.
get_health is provided by the Wellness Manager MCP server (wellnessagent/wellness-master). 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 →