Low Risk

caddy_list_sites

List all sites currently declared in the Caddyfile

How to control caddy_list_sites ↓

What caddy_list_sites does on Crow

AI agents call caddy_list_sites 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 caddy_list_sites needs a policy

This tool retrieves and displays existing Caddy web server site configurations. It performs no modifications, executions, or destructive actions—purely informational querying of configuration state. The blast radius of misuse is minimal: an attacker gains visibility into site configuration but cannot alter services or access sensitive data beyond what the configuration reveals.

From the tool's definition Tool name 'caddy_list_sites' and description 'List all sites currently declared in the Caddyfile' indicate a read-only query operation that retrieves configuration information without modification.

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

How to control caddy_list_sites

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 caddy_list_sites:

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

caddy_list_sites 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 caddy_list_sites

What does the caddy_list_sites tool do? +

List all sites currently declared in the Caddyfile. 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 caddy_list_sites? +

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

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

Can I rate-limit caddy_list_sites? +

Yes. Add a rate_limit block to the caddy_list_sites 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 caddy_list_sites completely? +

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

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