check_prometheus

Check Prometheus monitoring service health. Queries /-/healthy and /-/ready endpoints and returns status. Also fetches basic TSDB stats from /api/v1/status/tsdb if healthy.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/check-prometheus.md

WHAT IT DOES

What check_prometheus does on Mcp Nettools

AI agents call check_prometheus 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.

RISK

Why check_prometheus is rated Low

This tool performs diagnostic queries against a Prometheus monitoring service to assess its health and retrieve statistics. All operations are read-only: the /-/healthy and /-/ready endpoints are designed to report status without side effects, and the /api/v1/status/tsdb endpoint retrieves time series database statistics. There is no data modification, execution of arbitrary commands, deletion, or financial impact.

From the tool's definition Tool queries Prometheus health check endpoints (/-/healthy, /-/ready) and fetches TSDB stats (/api/v1/status/tsdb) — read-only monitoring endpoints that retrieve status information without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_prometheus 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_prometheus, this is the rule to start with:

check_prometheus Allowed

check_prometheus is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_prometheus": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_prometheus call is checked against it from then on.

FAQ

Questions about check_prometheus

What does the check_prometheus tool do? +

Check Prometheus monitoring service health. Queries /-/healthy and /-/ready endpoints and returns status. Also fetches basic TSDB stats from /api/v1/status/tsdb if healthy. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_prometheus? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_prometheus: 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.

What risk level is check_prometheus? +

check_prometheus is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_prometheus? +

Yes. Add a rate_limit block to the check_prometheus 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.

How do I block check_prometheus completely? +

Set action: deny in the PolicyLayer policy for check_prometheus. 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.

What MCP server provides check_prometheus? +

check_prometheus 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.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →