Check Coolify API health
AI agents call healthcheck to retrieve information from Coolify MCP Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A health check tool queries the API status to verify it is operational. This is a read-only operation with no ability to modify, execute, or destroy any data. Misuse has minimal blast radius.
From the tool's definition 'Check Coolify API health' - purely a read/status check operation with no side effects
Attacks that exploit this kind of access
Check Coolify API health. It is categorised as a Read tool in the Coolify MCP Tools MCP Server, which means it retrieves data without modifying state.
Register the Coolify MCP Tools MCP server in PolicyLayer and add a rule for healthcheck: 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 Coolify MCP Tools. Nothing to install.
healthcheck is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the healthcheck 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 healthcheck. 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.
healthcheck is provided by the Coolify MCP Tools MCP server (jplansink/coolify-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →