Low Risk

health_check

Check health of Ludus MCP server and Ludus API connectivity. Uses the ludus CLI if available for more reliable connectivity testing. Returns: Health status including: - Server status (healthy/unhealthy) - MCP version - Ludus API reachability - Connection latency - Number of available tools - Conf...

How to control health_check ↓

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

Low Risk

This is a diagnostic/monitoring tool that queries and reports system state without triggering any operational changes. It is purely informational and read-only, making it the lowest-risk category. Even if misused by an AI agent, it cannot cause harm—it only retrieves status information.

From the tool's definition Tool performs health status checks and connectivity testing with no side effects. Returns diagnostic information: 'Server status', 'MCP version', 'Ludus API reachability', 'Connection latency', 'Number of available tools', 'Configuration sources', 'Ludus…

Documented attack patterns abuse exactly the kind of access health_check gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Ludus FastMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for health_check:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "health_check": {}
  }
}

health_check is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Ludus FastMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the health_check tool do? +

Check health of Ludus MCP server and Ludus API connectivity. Uses the ludus CLI if available for more reliable connectivity testing. Returns: Health status including: - Server status (healthy/unhealthy) - MCP version - Ludus API reachability - Connection latency - Number of available tools - Configuration sources - Ludus server version (if connected). It is categorised as a Read tool in the Ludus FastMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on health_check? +

Register the Ludus Fast MCP server in PolicyLayer and add a rule for health_check: 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 Ludus FastMCP. Nothing to install.

What risk level is health_check? +

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

Can I rate-limit health_check? +

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

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

health_check is provided by the Ludus Fast MCP server (tjnull/ludus-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ludus FastMCP tool call.

Deterministic rules across all 201 Ludus FastMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

201 Ludus FastMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.