Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_allow_domain

Whitelist a domain to bypass block lists and resolve false positives in DNS filtering.

Instructions

Allow a domain name, bypassing any block lists. Useful for whitelisting false positives.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name to allow (e.g. plex.direct)

Implementation Reference

  • The handler function for dns_allow_domain tool. It validates the domain via validateDomain, calls /api/allowed/add on the TechnitiumClient, and returns a success response.
    definition: {
      name: "dns_allow_domain",
      description:
        "Allow a domain name, bypassing any block lists. Useful for whitelisting false positives.",
      inputSchema: {
        type: "object",
        properties: {
          domain: {
            type: "string",
            description: "Domain name to allow (e.g. plex.direct)",
          },
        },
        required: ["domain"],
      },
    },
    readonly: false,
    handler: async (args) => {
      const domain = validateDomain(args.domain as string);
      const data = await client.callOrThrow("/api/allowed/add", {
        domain,
      });
      return JSON.stringify(
        { success: true, allowed: domain, ...data },
        null,
        2
      );
    },
  • The input schema for dns_allow_domain, defining a required 'domain' string parameter.
    {
      definition: {
        name: "dns_allow_domain",
        description:
          "Allow a domain name, bypassing any block lists. Useful for whitelisting false positives.",
        inputSchema: {
          type: "object",
          properties: {
            domain: {
              type: "string",
              description: "Domain name to allow (e.g. plex.direct)",
            },
          },
          required: ["domain"],
        },
      },
  • src/tools/index.ts:7-7 (registration)
    Import of blockingTools which contains the dns_allow_domain tool.
    import { blockingTools } from "./blocking.js";
  • Spread of blockingTools into getAllTools array, registering dns_allow_domain.
    ...blockingTools(client),
  • Rate limiting configuration for dns_allow_domain (mutateLimits: 10 requests per 60s window).
    for (const tool of [
      "dns_create_zone", "dns_add_record", "dns_update_record",
      "dns_block_domain", "dns_allow_domain",
      "dns_remove_allowed", "dns_remove_blocked", "dns_delete_cached",
      "dns_enable_zone", "dns_disable_zone", "dns_set_zone_options",
      "dns_set_settings", "dns_install_app",
    ]) {
      this.toolLimits.set(tool, mutateLimits);
Behavior4/5

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

With no annotations, the description conveys the key behavior: allowing a domain and bypassing block lists. It is honest and direct, though it could mention persistence or permissions, but given simplicity it's sufficient.

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 with no wasted words. The action is front-loaded: 'Allow a domain name'. Perfectly concise for the tool's simplicity.

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 one-parameter tool with no output schema, the description covers purpose, usage, and behavior adequately. No gaps identified.

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 parameter description is already clear in the schema. The tool description adds no extra meaning beyond 'bypassing block lists', which is context rather than parameter detail. Baseline applies.

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 verb 'Allow' and resource 'domain name', and explains it bypasses block lists. It distinguishes itself from sibling tools like dns_block_domain and dns_remove_allowed by focusing on whitelisting false positives.

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

Usage Guidelines4/5

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

The description mentions 'useful for whitelisting false positives', providing usage context. However, it lacks explicit when-not-to-use guidance or direct comparison with siblings, though the context is clear enough for a simple tool.

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