caddy_cert_health

SERVERCrow SOURCEkh0pper/crow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/caddy-cert-health.md

WHAT IT DOES

What caddy_cert_health does on Crow

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

RISK

Why caddy_cert_health is rated Low

This tool queries and reports certificate health metrics without creating, modifying, deleting, executing commands, or moving money. It is purely observational, gathering diagnostic information about existing TLS certificates and their renewal status. While it could inform decisions about certificate management, the tool itself performs no side effects.

From the tool's definition Tool performs monitoring and reporting functions: 'Report TLS cert health', 'expiry', 'recent renewal failures', 'DNS A/AAAA mismatches'. The verbs indicate data retrieval and inspection without modification—checking status, surfacing existing information.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs caddy_cert_health 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_cert_health, this is the rule to start with:

caddy_cert_health Allowed

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "caddy_cert_health": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every caddy_cert_health call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →