check_influxdb
Check InfluxDB server health. Supports both InfluxDB v2 (GET /health → JSON status/pass) and v1 (GET /ping → 204 No Content). Returns version, status, and commit information when available. host: IP or hostname. port: default 8086. https: use HTTPS (default False).
This record as markdown: /tools/aaronckj-mcp-nettools/check-influxdb.md
What check_influxdb does on Mcp Nettools
AI agents call check_influxdb to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_influxdb is rated Low
This tool only retrieves health and status data from an InfluxDB server via HTTP GET requests. It has no side effects on the target system or data—it merely queries and returns diagnostic information. The blast radius is minimal as the tool cannot modify, delete, or execute any operations on the database or underlying infrastructure. It fits the 'Read' category as a retrieval/query operation.
From the tool's definition Tool performs 'Check InfluxDB server health' with GET requests to /health and /ping endpoints that return status information. No parameters allow modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs check_influxdb safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_influxdb, this is the rule to start with:
check_influxdb is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_influxdb call is checked against it from then on.
Questions about check_influxdb
Check InfluxDB server health. Supports both InfluxDB v2 (GET /health → JSON status/pass) and v1 (GET /ping → 204 No Content). Returns version, status, and commit information when available. host: IP or hostname. port: default 8086. https: use HTTPS (default False). It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_influxdb: 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 Nettools. Nothing to install.
check_influxdb 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_influxdb 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_influxdb. 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_influxdb is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue