This record as markdown: /tools/openclaw/health.md
What health does on OpenClaw
AI agents call health to retrieve information from OpenClaw without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why health is rated Low
This tool fetches diagnostic or status information from a running service (Gateway). It performs no side effects, does not modify data, and does not trigger external operations. It is a simple data retrieval operation typical of health check or monitoring endpoints. The low severity reflects minimal blast radius—even if misused by an agent, it can only retrieve information, not cause harm.
From the tool's definition Tool name 'health' and description 'Fetch detailed health from the running Gateway' indicates a read-only query operation that retrieves status/monitoring data without modifying state.
Attacks that exploit this kind of access
The rule that runs health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OpenClaw, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For health, this is the rule to start with:
health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect OpenClaw, apply this rule, and every health call is checked against it from then on.
Questions about health
Fetch detailed health from the running Gateway. It is categorised as a Read tool in the OpenClaw MCP Server, which means it retrieves data without modifying state.
Register the OpenClaw MCP server in PolicyLayer and add a rule for 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 OpenClaw. Nothing to install.
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 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 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.
health is provided by the OpenClaw MCP server (openclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on OpenClaw, and thousands of servers like it.
This server
Across the catalogue