caddy_reload_tool · Infra MCP: Risk & Policy

WHAT IT DOES

What caddy_reload_tool does on Infra

AI agents invoke caddy_reload_tool to trigger actions in Infra. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why caddy_reload_tool needs a policy

The tool executes a Caddy reload operation, which is a command that triggers an external system (the Caddy reverse proxy) to reconfigure itself. While the confirmation requirement (confirm=true) mitigates risk, the tool still Execute-class because it initiates active service operations.

From the tool's definition 'Reload Caddy after a Caddyfile change' — reloading a reverse proxy service triggers external operations (Caddy process restart) whose effects depend on configuration arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

caddy_reload_tool Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Infra, so you can run agents against it safely.

FAQ

Questions about caddy_reload_tool

What does the caddy_reload_tool tool do? +

Reload Caddy after a Caddyfile change. Requires confirm=true. It is categorised as a Execute tool in the Infra 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_reload_tool? +

Register the Infra MCP server in PolicyLayer and add a rule for caddy_reload_tool: 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 Infra. Nothing to install.

What risk level is caddy_reload_tool? +

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

Can I rate-limit caddy_reload_tool? +

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

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

caddy_reload_tool is provided by the Infra MCP server (odanree/infra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.