Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_delete_zone

Deletes a DNS zone and all associated records. Requires explicit confirmation to prevent accidental removal.

Instructions

Delete a DNS zone and all its records. Requires confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneYesZone domain name to delete
confirmNoMust be true to confirm deletion. Without this, returns a warning instead of deleting.

Implementation Reference

  • The handler function for dns_delete_zone that validates the domain, checks for confirmation (safety gate), and calls the API to delete the zone.
      handler: async (args) => {
        const zone = validateDomain(args.zone as string);
        if (args.confirm !== true) {
          return JSON.stringify(
            {
              warning: `This will permanently delete zone '${zone}' and ALL its records. Set confirm=true to proceed.`,
            },
            null,
            2
          );
        }
        const data = await client.callOrThrow("/api/zones/delete", { zone });
        return JSON.stringify(
          { success: true, deleted: zone, ...data },
          null,
          2
        );
      },
    },
  • The schema definition for dns_delete_zone including its name, description, and input parameters (zone required, confirm optional boolean).
    definition: {
      name: "dns_delete_zone",
      description:
        "Delete a DNS zone and all its records. Requires confirm=true to execute.",
      inputSchema: {
        type: "object",
        properties: {
          zone: {
            type: "string",
            description: "Zone domain name to delete",
          },
          confirm: {
            type: "boolean",
            description:
              "Must be true to confirm deletion. Without this, returns a warning instead of deleting.",
          },
        },
        required: ["zone"],
      },
  • Registration of zoneTools (which includes dns_delete_zone) via the zoneTools(client) call aggregated into all tools.
    export function getAllTools(client: TechnitiumClient): ToolEntry[] {
      return [
        ...dashboardTools(client),
        ...dnsClientTools(client),
        ...zoneTools(client),
        ...recordTools(client),
        ...blockingTools(client),
        ...cacheTools(client),
        ...settingsTools(client),
        ...logTools(client),
        ...appTools(client),
        ...dnssecTools(client),
      ];
    }
  • The validateDomain helper function used by dns_delete_zone handler to validate and sanitize the zone domain name.
    export function validateDomain(domain: string): string {
      if (!domain || typeof domain !== "string") {
        throw new Error("Domain name is required");
      }
      const trimmed = domain.trim().toLowerCase();
      if (trimmed.length > 253) {
        throw new Error("Domain name exceeds maximum length of 253 characters");
      }
      if (!DOMAIN_RE.test(trimmed)) {
        throw new Error("Invalid domain name format");
      }
      return trimmed;
    }
  • Rate limit registration for dns_delete_zone in the destructive operations category (5 requests per 60 seconds).
    for (const tool of [
      "dns_delete_zone", "dns_delete_record", "dns_flush_cache",
      "dns_flush_allowed", "dns_flush_blocked", "dns_uninstall_app",
      "dns_update_blocklists", "dns_temp_disable_blocking",
    ]) {
      this.toolLimits.set(tool, destructiveLimits);
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It states that deletion requires confirmation, but does not mention irreversibility, permission requirements, or side effects (e.g., all records permanently removed). For a destructive tool, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the main action and critical condition. No unnecessary words or repetition. Efficient for the agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given it's a simple two-parameter tool without output schema, the description covers the basics. However, it could be more complete by noting the permanent nature of the deletion or any prerequisites (e.g., zone must exist). The tool's destructive nature warrants a bit more context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters. The description adds meaning by explaining that confirm=true is required to execute, which goes beyond the schema's note that it 'must be true to confirm deletion.' This provides clear operational context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the action: delete a DNS zone and all its records. It uses a specific verb and resource, distinguishing it from sibling tools like dns_delete_record or dns_disable_zone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description mentions the confirm requirement but does not provide guidance on when to use this tool versus alternatives (e.g., dns_disable_zone for deactivation, or dns_create_zone for creation). No explicit 'when not to use' or reference to other tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rosschurchill/technitium-mcp-secure'

If you have feedback or need assistance with the MCP directory API, please join our Discord server