dozzle_status
Check whether the Dozzle log viewer is running and reachable
This record as markdown: /tools/kh0pper-crow/dozzle-status.md
What dozzle_status does on Crow
AI agents call dozzle_status to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why dozzle_status is rated Low
This tool performs a simple health/status check of the Dozzle log viewer service. It retrieves information about service availability and reachability with no side effects, no data modification, and no command execution. This is a read-only operation with minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name 'dozzle_status' and description 'Check whether the Dozzle log viewer is running and reachable' indicate a status check operation that queries the state of a service without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs dozzle_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dozzle_status, this is the rule to start with:
dozzle_status 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 Crow, apply this rule, and every dozzle_status call is checked against it from then on.
Questions about dozzle_status
Check whether the Dozzle log viewer is running and reachable. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for dozzle_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 Crow. Nothing to install.
dozzle_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 dozzle_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 dozzle_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.
dozzle_status is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue