caddy_remove_site
Remove a site block from the Caddyfile (matched by address) and reload Caddy. Destructive — the change is persisted to disk.
This record as markdown: /tools/kh0pper-crow/caddy-remove-site.md
What caddy_remove_site does on Crow
AI agents call caddy_remove_site to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why caddy_remove_site is rated Critical
This tool irreversibly deletes a site block from the Caddyfile configuration and persists that deletion to disk. The change cannot be automatically undone without manual intervention or version control recovery. While not causing data loss in the traditional sense, it removes operational infrastructure configuration in a way that disrupts service availability and cannot be reversed by the tool itself.
From the tool's definition Tool description explicitly states "Remove a site block from the Caddyfile" and "Destructive — the change is persisted to disk." The irreversible deletion of a site configuration and the explicit mention of destructive nature confirms this classification.
Attacks that exploit this kind of access
The rule that runs caddy_remove_site 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 caddy_remove_site, this is the rule to start with:
caddy_remove_site is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every caddy_remove_site call is checked against it from then on.
Questions about caddy_remove_site
Remove a site block from the Caddyfile (matched by address) and reload Caddy. Destructive — the change is persisted to disk. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for caddy_remove_site: 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.
caddy_remove_site is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the caddy_remove_site 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 caddy_remove_site. 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.
caddy_remove_site 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.
Across the catalogue