Perform a health check on the MCP server.
AI agents call health_check to retrieve information from MCP Log Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A health check is a diagnostic query that examines system state and returns status information. It has no side effects, does not modify data, does not execute arbitrary code, and does not delete or move resources. This is a standard read operation with minimal blast radius if misused—an attacker gains visibility into server status but cannot alter systems or data.
From the tool's definition Tool name 'health_check' and description 'Perform a health check on the MCP server' indicate a status query operation that retrieves diagnostic information without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Perform a health check on the MCP server. It is categorised as a Read tool in the MCP Log Analyzer MCP Server, which means it retrieves data without modifying state.
Register the MCP Log Analyzer 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 MCP Log Analyzer. 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 MCP Log Analyzer MCP server (sedwardstx/demomcp). 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 →