Skip to main content
Glama
rosschurchill

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
NameRequiredDescriptionDefault
confirmNoMust be true to confirm flush. Without this, returns a warning instead.

Implementation Reference

  • 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
      );
    },
  • 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.",
        },
      },
    },
  • 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
        );
      },
    },
  • 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),
      ];
  • 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);
    }
Behavior4/5

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

Without annotations, the description fully discloses the destructive action (removes all allowed domains) and the required confirmation (confirm=true). It is transparent about the behavior, though it could mention irreversibility more explicitly.

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-load the main purpose and add the required confirmation condition. Every sentence earns its place with no waste.

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

Completeness4/5

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

For a simple tool with one boolean parameter and no output schema, the description covers the core action and the required confirmation. It differentiates from siblings by specifying 'allow list'. It could mention any side effects (e.g., no undo), but overall it is adequate.

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 description adds minimal meaning beyond the schema's parameter description. The schema already explains that confirm must be true and that without it a warning is returned, so the description provides no additional semantic value.

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 action ('Flush') and the resource ('the entire allow list'), with 'all allowed domains will be removed' reinforcing the scope. It distinguishes from siblings like dns_flush_blocked and dns_flush_cache by specifying 'allow list'.

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 (when you want to clear all allowed domains) but does not explicitly state when to use this tool versus alternatives such as dns_remove_allowed for selective removal or dns_flush_blocked for blocked list. 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.

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