check_victoriametrics
Check VictoriaMetrics (time-series database) health via GET /health and retrieve /api/v1/status/tsdb summary. Returns healthy, version if available, and time series count. Default port 8428. Set https=True for HTTPS.
This record as markdown: /tools/aaronckj-mcp-nettools/check-victoriametrics.md
What check_victoriametrics does on Mcp Nettools
AI agents call check_victoriametrics 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_victoriametrics is rated Low
This tool only reads diagnostic and status information from a VictoriaMetrics instance. GET requests with no parameters that modify state are inherently read operations. The blast radius is minimal—worst case an agent could discover that a service is running, but cannot alter data, execute code, or cause harm. Classified as Read with low severity.
From the tool's definition Tool performs health checks via GET /health and retrieves /api/v1/status/tsdb summary with no capability to modify data. Described actions are 'check' and 'retrieve' which are read-only operations.
Attacks that exploit this kind of access
The rule that runs check_victoriametrics 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_victoriametrics, this is the rule to start with:
check_victoriametrics 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_victoriametrics call is checked against it from then on.
Questions about check_victoriametrics
Check VictoriaMetrics (time-series database) health via GET /health and retrieve /api/v1/status/tsdb summary. Returns healthy, version if available, and time series count. Default port 8428. Set https=True for HTTPS. 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_victoriametrics: 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_victoriametrics 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_victoriametrics 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_victoriametrics. 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_victoriametrics 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