caddy_stop

THE RISK

High Risk

Why caddy_stop needs a policy

This tool triggers an external operation (server shutdown) that has significant operational consequences. While the shutdown is graceful (not forced), it is an Execute action because it invokes a command-line-like operation on a running system whose effects are immediate and not trivially reversible within normal operations.

From the tool's definition Gracefully shut down the Caddy server.

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

POLICY

How to control caddy_stop

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "caddy_stop": {
      "limits": [
        {
          "counter": "caddy_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

caddy_stop stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Caddy — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Caddy tools

Destructive caddy_config_delete Delete config at a JSON path. Removes the config node at the specified path. Deleting a pa Destructive caddy_remove_route Remove a route. Target by @id (preferred — stable across reorderings) or by array index on Destructive caddy_load Replace the entire Caddy configuration atomically. Accepts a JSON config object, or a Cadd Write caddy_add_route Add a route with full control over match conditions and handlers. Supports any Caddy handl Write caddy_config_set Write config at a JSON path. Mode Write caddy_reverse_proxy Add a reverse proxy route. The most common operation — just specify where traffic comes fr Write caddy_revert Manage config snapshots for rollback. Snapshots are auto-captured before caddy_load and ke Write caddy_tls Get or configure TLS/HTTPS settings. Actions:

All 18 Caddy tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Caddy → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about caddy_stop

What does the caddy_stop tool do? +

Gracefully shut down the Caddy server. Requires confirm=true to prevent accidental shutdown. It is categorised as a Execute tool in the Caddy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on caddy_stop? +

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

What risk level is caddy_stop? +

caddy_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit caddy_stop? +

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

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

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

Enforce policy on every Caddy tool call.

Start from Caddy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →