Read NextDNS query analytics, then change blocking rules as approved steps
Connect NextDNS and your agent can read query analytics, blocking reasons, and the current allowlist for any profile without waiting on the dashboard. When a domain needs to be unblocked, denied, or rewritten, the change is proposed first and applied after you approve it. Authentication is by API key.
68 tools: 28 read, 40 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Nextdns run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as add allowlist entry, add blocked tld, add denylist domain, add parental control category, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Nextdns — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.