caddy_add_site
Add a reverse-proxy site block to the Caddyfile and reload. For anything beyond
This record as markdown: /tools/kh0pper-crow/caddy-add-site.md
What caddy_add_site does on Crow
AI agents use caddy_add_site to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why caddy_add_site is rated Medium
This tool modifies the Caddyfile (configuration file) by adding a new site block, which is a reversible write operation. The reload action triggers reconfiguration of the web server. While it affects production infrastructure, the changes are not permanent/destructive (can be removed or edited), making it Write rather than Execute or Destructive.
From the tool's definition Tool name 'caddy_add_site' and description 'Add a reverse-proxy site block to the Caddyfile and reload' explicitly indicates creation of a new configuration entry and triggering a reload operation.
Attacks that exploit this kind of access
The rule that runs caddy_add_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_add_site, this is the rule to start with:
caddy_add_site stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 caddy_add_site call is checked against it from then on.
Questions about caddy_add_site
Add a reverse-proxy site block to the Caddyfile and reload. For anything beyond. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for caddy_add_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_add_site is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the caddy_add_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_add_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_add_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.
This server
Across the catalogue