Technitium MCP Secure

dns_flush_allowed

Removes all allowed domains from the allow list. Requires confirm=true to execute.

Instructions

Flush the entire allow list. All allowed domains will be removed. Requires confirm=true to execute.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`confirm`	No	Must be true to confirm flush. Without this, returns a warning instead.

Implementation Reference

src/tools/blocking.ts:188-205 (handler)

The handler function for dns_flush_allowed. Checks confirm=true, then calls /api/allowed/flush to clear the allow list.

handler: async (args) => {
  if (args.confirm !== true) {
    return JSON.stringify(
      {
        warning:
          "This will remove ALL domains from the allow list. Set confirm=true to proceed.",
      },
      null,
      2
    );
  }
  const data = await client.callOrThrow("/api/allowed/flush");
  return JSON.stringify(
    { success: true, message: "Allow list flushed", ...data },
    null,
    2
  );
},

src/tools/blocking.ts:176-185 (schema)

Input schema for dns_flush_allowed defining the 'confirm' boolean parameter.

inputSchema: {
  type: "object",
  properties: {
    confirm: {
      type: "boolean",
      description:
        "Must be true to confirm flush. Without this, returns a warning instead.",
    },
  },
},

src/tools/blocking.ts:171-206 (registration)

Tool definition registration for dns_flush_allowed including name, description, inputSchema, and readonly flag.

{
  definition: {
    name: "dns_flush_allowed",
    description:
      "Flush the entire allow list. All allowed domains will be removed. Requires confirm=true to execute.",
    inputSchema: {
      type: "object",
      properties: {
        confirm: {
          type: "boolean",
          description:
            "Must be true to confirm flush. Without this, returns a warning instead.",
        },
      },
    },
  },
  readonly: false,
  handler: async (args) => {
    if (args.confirm !== true) {
      return JSON.stringify(
        {
          warning:
            "This will remove ALL domains from the allow list. Set confirm=true to proceed.",
        },
        null,
        2
      );
    }
    const data = await client.callOrThrow("/api/allowed/flush");
    return JSON.stringify(
      { success: true, message: "Allow list flushed", ...data },
      null,
      2
    );
  },
},

src/tools/index.ts:14-26 (registration)

getAllTools aggregates blockingTools (which includes dns_flush_allowed) into the full tool list.

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),
  ];

src/rate-limit.ts:25-31 (helper)

Rate limit configuration: dns_flush_allowed is placed in the destructive operations group (5 requests per 60s window).

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);
}

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.2.0May 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the destructive effect ('All allowed domains will be removed') and the confirmation requirement ('Requires confirm=true to execute'). However, it does not mention whether the action is reversible or how the system responds when confirm is false, though the schema partially covers this.

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 concise sentences front-load the primary action and effect, then add the safety condition. No wasted words or redundant details.

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

Completeness5/5

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

For a simple, destructive flush operation, the description adequately covers purpose, effect, and the single parameter's behavior. No output schema is needed, and the existing schema completes the parameter context.

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

Parameters3/5

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

Schema coverage is 100%, and the schema already fully describes the confirm parameter. The description adds no new semantic information beyond restating that confirm=true is required, so it does not exceed the baseline for high schema coverage.

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?

The description clearly states the tool flushes the entire allow list and that all allowed domains will be removed. It uses a specific verb ('flush') and resource ('allow list'), distinguishing it from related tools like dns_remove_allowed.

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?

The description implies usage for removing all allowed domains, but it does not explicitly contrast with dns_remove_allowed or other alternatives. No when-not-to-use guidance is provided.

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