Convert a config in any registered adapter format to Caddy JSON without loading it. Useful for previewing what a Caddyfile produces, or for porting from nginx/yaml configs when Caddy is built with the matching adapter module (
AI agents call caddy_adapt to retrieve information from Caddy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
caddy_adapt is a read-only transformation tool that converts configuration formats for preview purposes. It performs no side effects, makes no modifications to the Caddy server, and does not apply or persist any configuration. This is a data retrieval and transformation operation with zero risk of unintended consequences even if misused by an agent.
From the tool's definition Tool description states it 'Convert[s] a config in any registered adapter format to Caddy JSON without loading it' and emphasizes it is 'Useful for previewing' — no changes are persisted, no configuration is applied, and explicitly no loading occurs.
Documented attack patterns abuse exactly the kind of access caddy_adapt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Caddy, and nothing reaches the server without passing your rules. This is the rule we recommend for caddy_adapt:
{
"version": "1",
"default": "deny",
"tools": {
"caddy_adapt": {}
}
} caddy_adapt is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Convert a config in any registered adapter format to Caddy JSON without loading it. Useful for previewing what a Caddyfile produces, or for porting from nginx/yaml configs when Caddy is built with the matching adapter module (. It is categorised as a Read tool in the Caddy MCP Server, which means it retrieves data without modifying state.
Register the Caddy MCP server in PolicyLayer and add a rule for caddy_adapt: 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 Caddy. Nothing to install.
caddy_adapt 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 caddy_adapt 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_adapt. 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_adapt is provided by the Caddy MCP server (yawlabs/caddy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Caddy, 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.
18 Caddy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.