health_checks
Run health checks on all VMs in the range.
This record as markdown: /tools/tjnull-ludus-fastmcp/health-checks.md
What health_checks does on Ludus FastMCP
AI agents invoke health_checks to trigger actions in Ludus FastMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why health_checks is rated High
The tool executes health check operations against VMs, which constitutes running commands/checks whose effects depend on the range state and VM configuration. This is not merely retrieving data (which would be Read), but actively triggering diagnostic operations on infrastructure.
From the tool's definition Runs health checks on all VMs in the range. This actively triggers operations (health check processes) on external resources (VMs).
Attacks that exploit this kind of access
The rule that runs health_checks 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_checks, this is the rule to start with:
health_checks stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ludus FastMCP, apply this rule, and every health_checks call is checked against it from then on.
Questions about health_checks
Run health checks on all VMs in the range. It is categorised as a Execute tool in the Ludus FastMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for health_checks: 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.
health_checks is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the health_checks 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.
Set action: deny in the PolicyLayer policy for health_checks. 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.
health_checks 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.
More on Ludus Fast, and thousands of servers like it.
Across the catalogue