Check current connection status to the InfluxDB instance. Returns connection status, configuration, and available endpoint results. Health assessment is flexible - if any check passes (client initialization, /health endpoint, or /ping), the instance is considered healthy. Available checks depend ...
AI agents call health_check to retrieve information from InfluxDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The health_check tool performs a passive diagnostic operation that reads and returns status information about the InfluxDB instance. It does not modify, create, delete, or execute any data-altering operations. The tool merely verifies connectivity and retrieves existing configuration/status data, which aligns with the Read category.
From the tool's definition Tool description states it 'Check[s] current connection status' and 'Returns connection status, configuration, and available endpoint results.' These are query/diagnostic operations with no side effects.
Attacks that exploit this kind of access
Check current connection status to the InfluxDB instance. Returns connection status, configuration, and available endpoint results. Health assessment is flexible - if any check passes (client initialization, /health endpoint, or /ping), the instance is considered healthy. Available checks depend on the InfluxDB product type and token configuration. It is categorised as a Read tool in the InfluxDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the InfluxDB MCP Server 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 InfluxDB MCP Server. 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 InfluxDB MCP Server MCP server (quorralyne/mcp_test_server). 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 →