Low Risk

dozzle_container_url

Build a Dozzle URL that deep-links straight to a container

How to control dozzle_container_url ↓

What dozzle_container_url does on Crow

AI agents call dozzle_container_url to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why dozzle_container_url needs a policy

This tool constructs a URL pointing to a container's Dozzle log viewer. It only builds/returns a URL string — a read/query operation with no side effects. No data is modified, executed, or deleted. Severity is low since generating a URL has minimal blast radius.

From the tool's definition Build a Dozzle URL that deep-links straight to a container

Documented attack patterns abuse exactly the kind of access dozzle_container_url gives an agent:

How to control dozzle_container_url

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for dozzle_container_url:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "dozzle_container_url": {}
  }
}

dozzle_container_url is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about dozzle_container_url

What does the dozzle_container_url tool do? +

Build a Dozzle URL that deep-links straight to a container. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dozzle_container_url? +

Register the Crow MCP server in PolicyLayer and add a rule for dozzle_container_url: 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.

What risk level is dozzle_container_url? +

dozzle_container_url is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dozzle_container_url? +

Yes. Add a rate_limit block to the dozzle_container_url 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.

How do I block dozzle_container_url completely? +

Set action: deny in the PolicyLayer policy for dozzle_container_url. 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.

What MCP server provides dozzle_container_url? +

dozzle_container_url 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.

Enforce policy on every Crow tool call.

Start from Crow, 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.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.