MCP & AI Agent Integration

Control D
automation.

19 AI agent actions for Control D — callable from any MCP-compatible runtime, Claude, Cursor, or Cerebral OS workflow. Use Control D to organize files, generate documents, and manage permissions programmatically. Full governance, audit trail, and dry-run safety on every execution.

No credit card required
Live in production environments
<200ms median execution
Dry-run before production
Execution trace
live
19
actions
100%
governed
<200ms
latency
19
AI agent actions
9
Read operations
10
Write operations
3
High-risk actions (approval gated)
Files & Documents Control D is a Files & Documents integration — use it to automate file storage, sharing, and document management from any AI agent or MCP-compatible runtime.
Actions

What you can do
with Control D.

Every action below is available as an MCP tool and a verb in Cerebral OS — callable from any AI agent, Claude, Cursor, Windsurf, or your own runtime via the BYOA API. All executions are governed, audited, and dry-run safe.

Get Account
control_d:get_account
Get current account information including subscription details and usage.
Read Low risk
Get Analytics
control_d:get_analytics
Get DNS query analytics and blocking statistics.
Read Low risk
Get Device
control_d:get_device
Fetch a single device by ID with its configuration and status.
Read Low risk
Get Profile
control_d:get_profile
Fetch a single profile by ID with its filtering rules and configuration.
Read Low risk
Get Rule
control_d:get_rule
Fetch a single filtering rule by ID with its configuration.
Read Low risk
List Devices
control_d:list_devices
List all devices with their basic information and status.
Read Low risk
List Profiles
control_d:list_profiles
List all filtering profiles with their basic information.
Read Low risk
List Resolvers
control_d:list_resolvers
List available DNS resolvers with their locations and capabilities.
Read Low risk
List Rules
control_d:list_rules
List filtering rules with optional filters.
Read Low risk
Create Device
control_d:create_device
Create a new device with the specified configuration.
Write Medium risk
Create Profile
control_d:create_profile
Create a new filtering profile with specified rules.
Write Medium risk
Create Rule
control_d:create_rule
Create a new filtering rule for a domain.
Write Medium risk
Delete Device
control_d:delete_device
Delete a device permanently. This action cannot be undone.
Write High risk
Delete Profile
control_d:delete_profile
Delete a filtering profile permanently. This action cannot be undone.
Write High risk
Delete Rule
control_d:delete_rule
Delete a filtering rule permanently. This action cannot be undone.
Write High risk
Test Connection
control_d:test_connection
Test the API connection and validate credentials.
Write Low risk
Update Device
control_d:update_device
Update an existing device's configuration.
Write Medium risk
Update Profile
control_d:update_profile
Update an existing filtering profile's configuration.
Write Medium risk
Update Rule
control_d:update_rule
Update an existing filtering rule's configuration.
Write Medium risk
MCP & Runtime API

Call Control D
from any AI agent.

Any AI agent — Claude, Cursor, LangChain, AutoGen, or your own — can call Control D actions through the Cerebral OS Runtime API. Governance, credentials, and audit trail fire automatically.

control_d:get_account READ
# Call via Runtime API
curl
-X POST \
  "https://api.cerebralos.com/v1/runtime/actions/run"
  -H "X-API-Key: YOUR_KEY" \
  -d '{
    "verb": "control_d:get_account",
    "args": {},
    "execution_id": "agent-001"
  }'
control_d:create_device WRITE
# Dry-run first — no production risk
curl
-X POST \
  "https://api.cerebralos.com/v1/runtime/actions/run"
  -H "X-API-Key: YOUR_KEY" \
  -d '{
    "verb": "control_d:create_device",
    "args": {},
    "execution_id": "agent-001",
    "metadata": {"dryRun": true}
  }'
Get your Runtime API key at app.cerebralos.com/signup — 1,000 free executions, no credit card required.
AI agent examples

What your AI agent
can do with Control D.

Real patterns your AI agent can execute via MCP or the Runtime API. Every action governed, dry-run safe, and fully audited.

Trigger
AI agent needs Control D data
Call control_d:get_account via MCP or Runtime API
AI processes result and takes next action
Full execution logged to audit trail automatically
Trigger
Workflow needs to write to Control D
Dry-run validates control_d:create_device before execution
Approval gate fires if risk level is high
Action executes with full governance — logged, audited, reversible
Trigger
File or document event
Process with AI
Route for approval
Notify team
How it works

Every Control D action
governed end-to-end.

Cerebral OS isn't a connector. It's the execution layer that sits in front of Control D — adding governance, dry-run safety, and a full audit trail to every operation.

Governance first
Every verb carries a risk classification. High-risk writes require explicit approval gates before they execute in production.
Dry-run safe
Simulate any Control D action before it touches production. See exactly what would happen before a single real call is made.
Immutable audit trail
Every Control D action is logged — what ran, what changed, who approved it, when it happened. Full history on every verb, forever.
Connect with

Control D works best
alongside these.

Build multi-step workflows that connect Control D to the rest of your stack. All governed. All audited.

Control D integration

Start free.
No credit card required.

Start free with 1,000 runs — no credit card required. Connect Control D in minutes, dry-run every action before it touches production, full audit trail on everything.

Start free — 1,000 runs Browse all integrations →