Check if the OpenClaw daemon is running and healthy
AI agents call daemon_status to retrieve information from ClawDaemon MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system health/status information without modifying, executing, or deleting anything. It is a passive diagnostic query analogous to a health check endpoint. Even in the context of an automation daemon, querying its status poses minimal risk. Severity is low because misuse would only return information about the daemon's operational state, not enable harmful actions directly.
From the tool's definition Tool is named 'daemon_status' and described as checking if the daemon is 'running and healthy' — a pure status query with no side effects.
Attacks that exploit this kind of access
Check if the OpenClaw daemon is running and healthy. It is categorised as a Read tool in the ClawDaemon MCP MCP Server, which means it retrieves data without modifying state.
Register the ClawDaemon MCP server in PolicyLayer and add a rule for daemon_status: 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 ClawDaemon MCP. Nothing to install.
daemon_status 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 daemon_status 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 daemon_status. 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.
daemon_status is provided by the ClawDaemon MCP server (mordiaky/clawdaemon-mcp). 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 →