remove_subdomain

Remove a subdomain from a hosting package

SERVER20i MCP Server SOURCEcbrown35/20i-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cbrown35-20i-mcp/remove-subdomain.md

WHAT IT DOES

What remove_subdomain does on 20i MCP Server

AI agents call remove_subdomain to permanently remove resources in 20i MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_subdomain is rated Critical

Removing a subdomain deletes its DNS records and configuration permanently, which cannot be undone without manual restoration. This is an irreversible operation affecting hosted services. While not as critical as database deletion, it causes direct service disruption and data loss (DNS configuration).

From the tool's definition Tool name 'remove_subdomain' with description 'Remove a subdomain from a hosting package' indicates irreversible deletion of DNS/subdomain configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_subdomain safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_subdomain, this is the rule to start with:

remove_subdomain Hidden

remove_subdomain is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_subdomain"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every remove_subdomain call is checked against it from then on.

FAQ

Questions about remove_subdomain

What does the remove_subdomain tool do? +

Remove a subdomain from a hosting package. It is categorised as a Destructive tool in the 20i MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_subdomain? +

Register the 20i MCP Server MCP server in PolicyLayer and add a rule for remove_subdomain: 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 20i MCP Server. Nothing to install.

What risk level is remove_subdomain? +

remove_subdomain is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_subdomain? +

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

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

remove_subdomain is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 20i MCP Server, and thousands of servers like it.

This server

All 302 20i MCP Server tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →delete_subdomain on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →