check_gatus

Check Gatus health monitoring dashboard reachability via GET /health. Returns healthy=true when all configured endpoints are up. Default port 8080.

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

WHAT IT DOES

What check_gatus does on Mcp Nettools

AI agents call check_gatus 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_gatus is rated Low

This tool retrieves status information from a Gatus health monitoring dashboard without side effects. It is a passive diagnostic query that checks if a service is reachable and healthy. Even if an AI agent misuses it by checking many endpoints, the blast radius is minimal—it only performs read-only HTTP GET requests with no capability to modify, delete, or execute code.

From the tool's definition Tool performs a GET request to check health status ('GET /health') and returns reachability information. No modification, deletion, or execution of commands occurs.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_gatus Allowed

check_gatus 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_gatus": {}
  }
}

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

FAQ

Questions about check_gatus

What does the check_gatus tool do? +

Check Gatus health monitoring dashboard reachability via GET /health. Returns healthy=true when all configured endpoints are up. Default port 8080. 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_gatus? +

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

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

Can I rate-limit check_gatus? +

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

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

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