AI agents call check_health to retrieve information from Grafana Mcp Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a health check on a service connection, which is a read-only diagnostic query. It retrieves status information without creating, modifying, deleting, or executing arbitrary operations. The description explicitly frames it as a troubleshooting tool for checking connectivity state, which has no blast radius if misused by an AI agent—it cannot modify data, execute code, or cause irreversible changes.
From the tool's definition Tool name 'check_health' and description indicating it checks Grafana service connection status for troubleshooting purposes ('检查Grafana服务连接状态（故障排查时使用）'). This is a diagnostic read-only operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access check_health gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Grafana Mcp Analyzer, and nothing reaches the server without passing your rules. This is the rule we recommend for check_health:
{
"version": "1",
"default": "deny",
"tools": {
"check_health": {}
}
}check_health is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
检查Grafana服务连接状态（故障排查时使用）. It is categorised as a Read tool in the Grafana Mcp Analyzer MCP Server, which means it retrieves data without modifying state.
Register the Grafana Mcp Analyzer MCP server in PolicyLayer and add a rule for check_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 Grafana Mcp Analyzer. Nothing to install.
check_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 check_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 check_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.
check_health is provided by the Grafana Mcp Analyzer MCP server (sailingcoder/grafana-mcp-analyzer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Grafana Mcp Analyzer tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Grafana Mcp Analyzer tools catalogued and risk-classified — across an index of 42,500+ MCP servers.