add_domain
Attach a custom domain to a DenkOps project. Returns the _denkops-verify TXT record token to set at your DNS provider, then run verify_domain.
This record as markdown: /tools/denkopsai-mcp/add-domain.md
What add_domain does on Denkopsai
AI agents use add_domain to create or update resources in Denkopsai, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Denkopsai environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | |
project_id | string | Yes |
Parameters from the server's own tool schema.
Why add_domain is rated Medium
This tool creates a new association between a custom domain and a DenkOps project by initiating a domain attachment workflow. While it involves DNS configuration, the action is reversible—a domain attachment can be undone. This is Write-category activity rather than Execute because it modifies data/configuration rather than running arbitrary code.
From the tool's definition Tool name 'add_domain' and description 'Attach a custom domain to a DenkOps project' indicate creation/modification of project configuration.
Attacks that exploit this kind of access
The rule that runs add_domain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_domain, this is the rule to start with:
add_domain 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Denkopsai, apply this rule, and every add_domain call is checked against it from then on.
Questions about add_domain
Attach a custom domain to a DenkOps project. Returns the _denkops-verify TXT record token to set at your DNS provider, then run verify_domain. It is categorised as a Write tool in the Denkopsai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_domain accepts 2 parameters: domain, project_id. Required: domain, project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai MCP server in PolicyLayer and add a rule for add_domain: 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 Denkopsai. Nothing to install.
add_domain is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_domain 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.
Set action: deny in the PolicyLayer policy for add_domain. 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.
add_domain is provided by the Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denkopsai, and thousands of servers like it.
This server
Across the catalogue