caddy_set_wellknown

Add or replace a standalone /.well-known/ handler at a domain that does NOT otherwise proxy to the federated app. Use this on an apex domain to delegate Matrix federation via

SERVERCrow SOURCEkh0pper/crow

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/caddy-set-wellknown.md

WHAT IT DOES

What caddy_set_wellknown does on Crow

AI agents use caddy_set_wellknown to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.

RISK

Why caddy_set_wellknown is rated Medium

This tool modifies web server configuration by adding or replacing a .well-known handler at a domain. This is a reversible Write operation (can be modified or removed later) rather than Destructive. The severity is high because misconfiguration could break federation, authentication, or trust relationships (e.g., Matrix federation, ACME challenges, OpenID discovery), affecting multiple users and services.

From the tool's definition Tool description states 'Add or replace a standalone /.well-known/ handler' and 'caddy_set_wellknown' name indicates modification of web server configuration. The words 'Add or replace' indicate data creation and modification operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

caddy_set_wellknown Rate-limited

caddy_set_wellknown stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_set_wellknown": {
      "limits": [
        {
          "counter": "caddy_set_wellknown_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about caddy_set_wellknown

What does the caddy_set_wellknown tool do? +

Add or replace a standalone /.well-known/ handler at a domain that does NOT otherwise proxy to the federated app. Use this on an apex domain to delegate Matrix federation via. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on caddy_set_wellknown? +

Register the Crow MCP server in PolicyLayer and add a rule for caddy_set_wellknown: 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_set_wellknown? +

caddy_set_wellknown is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit caddy_set_wellknown? +

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

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

caddy_set_wellknown 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

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →