Read your DNS policy state, then change it as an approved step
Control D holds the DNS policy for your fleet: which endpoints resolve, what they can reach, and when. Luumen reads devices, profiles, organization membership, and resolver access IPs on request, so you can answer a question without opening the dashboard. Changes — a new blocking rule, a device edit, a profile clone — are previewed and sent for approval first.
54 tools: 33 read, 21 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Control D 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.
Read actions answer immediately. Anything that writes — delete device by id, delete profile, delete profile rule by rule id, delete rule from folder, and more — is shown as a plan and requires approval by default, including the 5 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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 Control D — 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.