AI agents call health_check to retrieve information from A-Modular-Kingdom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the operational state of the server and its components, returning diagnostic information. It performs no modifications, deletions, code execution, or financial operations. It is a passive monitoring/diagnostic tool typical of production systems. Categorized as Read with low severity since misuse poses minimal risk—an agent cannot cause harm by repeatedly checking health status.
From the tool's definition Tool name 'health_check' and description 'Check MCP server health and component status' indicate retrieval of status information with no side effects.
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 A-Modular-Kingdom, and nothing reaches the server without passing your rules. This is the rule we recommend for health_check:
{
"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.
Free to start. No card required.
Check MCP server health and component status. It is categorised as a Read tool in the A-Modular-Kingdom MCP Server, which means it retrieves data without modifying state.
Register the A-Modular-Kingdom 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 A-Modular-Kingdom. Nothing to install.
health_check 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 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.
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.
health_check is provided by the A-Modular-Kingdom MCP server (masihmoafi/a-modular-kingdom). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from A-Modular-Kingdom, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 A-Modular-Kingdom tools catalogued and risk-classified — across an index of 43,000+ MCP servers.