Low Risk

caddy_cert_health

Report TLS cert health across all configured sites: ok / warning / error per domain, with expiry, ACME issuer, recent renewal failures, and DNS A/AAAA mismatches. Surfaces renewal failures that would otherwise be silent.

How to control caddy_cert_health ↓

What caddy_cert_health does on Crow

AI agents call caddy_cert_health to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why caddy_cert_health needs a policy

This is a read-only monitoring and diagnostic tool that retrieves certificate status information without creating, modifying, or deleting any resources. It has minimal blast radius if misused by an AI agent—the worst case is querying sensitive infrastructure details, which is typical low-risk information disclosure. The tool surfaces existing failure states rather than causing them.

From the tool's definition The tool 'caddy_cert_health' reports TLS certificate health status ('ok / warning / error'), expiry dates, ACME issuer information, renewal failures, and DNS mismatches.

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

How to control caddy_cert_health

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for caddy_cert_health:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "caddy_cert_health": {}
  }
}

caddy_cert_health is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about caddy_cert_health

What does the caddy_cert_health tool do? +

Report TLS cert health across all configured sites: ok / warning / error per domain, with expiry, ACME issuer, recent renewal failures, and DNS A/AAAA mismatches. Surfaces renewal failures that would otherwise be silent. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on caddy_cert_health? +

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

What risk level is caddy_cert_health? +

caddy_cert_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit caddy_cert_health? +

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

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

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

Enforce policy on every Crow tool call.

Start from Crow, 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.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.