health_check

What health_check does on Ludus FastMCP

AI agents call health_check to retrieve information from Ludus FastMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why health_check is rated Low

Health checks are inherently read-only operations that query the state of resources without modifying them. Even if it triggers internal diagnostics, it returns status information without altering data or executing external commands. The lack of description lowers confidence slightly, but the semantic meaning of 'health_check' is unambiguous in infrastructure management contexts.

From the tool's definition Tool name 'health_check' indicates a status query operation with no side effects. The empty description prevents direct confirmation, but the naming convention strongly suggests checking system/service health without modification.

The rule that runs health_check safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ludus FastMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health_check, this is the rule to start with:

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

Questions about health_check