This record as markdown: /tools/denkopsai-mcp/remove-domain.md
What remove_domain does on Denkopsai
AI agents call remove_domain to permanently remove resources in Denkopsai, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain_id | string | Yes | |
project_id | string | Yes |
Parameters from the server's own tool schema.
Why remove_domain is rated Critical
Detaching a domain is a destructive operation that cannot be easily undone without manual reconfiguration. This action could break service availability, interrupt DNS resolution, and require domain re-attachment and propagation—making it more severe than a simple Write operation. The high severity reflects the potential for significant operational disruption if misused by an agent.
From the tool's definition Tool name 'remove_domain' and description 'Detach a custom domain from a DenkOps project' indicate an irreversible action that severs the association between a domain and project infrastructure.
Attacks that exploit this kind of access
The rule that runs remove_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 remove_domain, this is the rule to start with:
remove_domain is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Denkopsai, apply this rule, and every remove_domain call is checked against it from then on.
Questions about remove_domain
Detach a custom domain from a DenkOps project. It is categorised as a Destructive tool in the Denkopsai MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_domain accepts 2 parameters: domain_id, project_id. Required: domain_id, 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 remove_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.
remove_domain is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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.
Across the catalogue