Run health checks on all VMs in the range. Args: user_id: Optional user ID (admin only) Returns: Health check results for all VMs
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.
Health checks are executable actions that probe VM states and trigger monitoring operations. While non-destructive and read-focused in intent, the tool actively executes external operations on managed infrastructure rather than passively querying state.
From the tool's definition Tool performs 'Run health checks on all VMs in the range' - a dynamic operational action that triggers external operations (VM health monitoring) whose effects depend on the range context and argument (user_id).
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access health_checks 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_checks:
{
"version": "1",
"default": "deny",
"tools": {
"health_checks": {
"limits": [
{
"counter": "health_checks_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Run health checks on all VMs in the range. Args: user_id: Optional user ID (admin only) Returns: Health check results for all VMs. 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.
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.