Check if Listmonk server is healthy and accessible.
AI agents call check_listmonk_health to retrieve information from Listmonk MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a health check—a read-only diagnostic operation that queries the server state and returns availability/status information. It has no side effects, creates no data, executes no commands, and cannot cause harm. It is a simple monitoring/discovery operation typical of health-check endpoints.
From the tool's definition Tool name 'check_listmonk_health' and description 'Check if Listmonk server is healthy and accessible' indicate a query operation that retrieves server status without modifying any data.
Documented attack patterns abuse exactly the kind of access check_listmonk_health gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Listmonk MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_listmonk_health:
{
"version": "1",
"default": "deny",
"tools": {
"check_listmonk_health": {}
}
}check_listmonk_health is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if Listmonk server is healthy and accessible. It is categorised as a Read tool in the Listmonk MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Listmonk MCP Server MCP server in PolicyLayer and add a rule for check_listmonk_health: 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 Listmonk MCP Server. Nothing to install.
check_listmonk_health 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 check_listmonk_health 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 check_listmonk_health. 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.
check_listmonk_health is provided by the Listmonk MCP Server MCP server (rhnvrm/listmonk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Listmonk MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Listmonk MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.