Check health of semantic layer and database connections.
AI agents call health_check to retrieve information from Ai Analyst without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Health checks are informational queries that retrieve status information about system components. They have no side effects, do not modify data, do not execute user-supplied code or commands, and do not delete or move resources. This is a classic Read category tool with minimal risk—the worst outcome of misuse would be gathering system status information, which has negligible blast radius.
From the tool's definition Tool name 'health_check' and description 'Check health of semantic layer and database connections' indicate a read-only diagnostic operation that queries status without modifying any data or executing arbitrary code.
Attacks that exploit this kind of access
Check health of semantic layer and database connections. It is categorised as a Read tool in the Ai Analyst MCP Server, which means it retrieves data without modifying state.
Register the Ai Analyst 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 Ai Analyst. 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 Ai Analyst MCP server (sbdk-dev/local-ai-analyst). 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 →