check_alertmanager

Check Prometheus Alertmanager health via GET /-/healthy and /-/ready. Returns health/readiness status and version from the API.

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-alertmanager.md

WHAT IT DOES

What check_alertmanager does on Mcp Nettools

AI agents call check_alertmanager 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_alertmanager is rated Low

This tool only retrieves diagnostic health and readiness status from an existing service via GET requests. It does not create, modify, delete, or execute any code or commands. It is purely informational and has minimal blast radius if misused.

From the tool's definition Tool performs GET requests to Prometheus Alertmanager health check endpoints (/-/healthy and /-/ready) which are read-only operations that query status and version information with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_alertmanager Allowed

check_alertmanager 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_alertmanager": {}
  }
}

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_alertmanager call is checked against it from then on.

FAQ

Questions about check_alertmanager

What does the check_alertmanager tool do? +

Check Prometheus Alertmanager health via GET /-/healthy and /-/ready. Returns health/readiness status and version from the API. 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_alertmanager? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_alertmanager: 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_alertmanager? +

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

Can I rate-limit check_alertmanager? +

Yes. Add a rate_limit block to the check_alertmanager 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_alertmanager completely? +

Set action: deny in the PolicyLayer policy for check_alertmanager. 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_alertmanager? +

check_alertmanager 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 →