---
title: "Control D integration for LuumenAI"
url: "https://www.luumen.ai/integrations/control-d/"
entity: SoftwareIntegration
category: "Identity & security"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Control D integration for LuumenAI

Read your DNS policy state, then change it as an approved step

## What LuumenAI can do with Control D

LuumenAI connects to Control D with an API token and exposes 54 tools (33 read-only · 16 write · 5 destructive). Reads answer immediately; writes are shown as a plan and require approval by default, configurable per tool by an administrator.

## Key facts

- Authentication: API token
- Tools available: 54 tools (33 read-only · 16 write · 5 destructive)
- Plan: available on all plans
- Category: Identity & security

## About Control D with LuumenAI

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.

## Example tools

Read-only (33 in total):

- `CONTROL_D_GET_ACCESS` — List up to the latest 50 IP addresses that were used to query against a specific Device (resolver).
- `CONTROL_D_GET_ANALYTICS_ENDPOINTS` — List analytics storage regions and their endpoints.
- `CONTROL_D_GET_ANALYTICS_LEVELS` — Retrieve available analytics log levels for Control D devices.
- `CONTROL_D_GET_BILLING_PAYMENTS` — Retrieve billing history of all payments made.
- `CONTROL_D_GET_BILLING_PRODUCTS` — Retrieve all products currently activated on the Control D account.
- `CONTROL_D_GET_DEVICES` — Lists all Control D devices (endpoints) associated with the account.
- `CONTROL_D_GET_DEVICES_TYPES` — List all allowed device types in Control D.
- `CONTROL_D_GET_IP` — Retrieve the current IP address and datacenter information for the API request.

Write and destructive (21 in total, approval required by default):

- `CONTROL_D_DELETE_DEVICES_DEVICE_ID` — Permanently delete a Control-D device/endpoint by its ID.
- `CONTROL_D_DELETE_PROFILES_PROFILE_ID` — Permanently deletes a Control D profile by its unique identifier (PK).
- `CONTROL_D_DELETE_PROFILES_PROFILE_ID_RULES_RULE_ID` — Delete a custom DNS rule from a Control D profile by its rule identifier (hostname/domain).
- `CONTROL_D_DELETE_PROFILES_PROFILE_ID_RULES_RULE_ID_FOLDER_ID` — Delete a custom DNS rule from a specific folder in a Control D profile.
- `CONTROL_D_DELETE_PROFILES_PROFILE_ID_SCHEDULES_SCHEDULE_ID` — Delete a specific schedule within a profile.
- `CONTROL_D_POST_DEVICES` — Create a new device (DNS endpoint) in Control D.
- `CONTROL_D_POST_PROFILES` — Create a new blank profile or clone an existing one.
- `CONTROL_D_POST_PROFILES_PROFILE_ID_RULES` — Create custom DNS rules for a profile to control domain resolution.

## Frequently asked questions

### How does LuumenAI connect to Control D?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Control D on its own?

Read actions answer immediately. Anything that writes is shown as a plan and requires approval by default, including the 5 actions classified as destructive. Administrators configure that per tool.

### Is there an audit trail?

Every call to Control D — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/control-d/