Control D MCP integration for AI agents.
Connect AI agents to Control D through 8 structured actions, including get current ip, upsert profile rule, and delete profile rule. Review authentication, i…
- ACTION CONTRACTS
- 8
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Control D integration exposes
The Control D Agent App exposes 8 provider-backed actions for security and developer tools work. Its current contract lets an authorized agent return the current ip address and datacenter seen by the control d api for troubleshooting api token allowed-ip issues, create or replace root-folder custom dns rules on a control d profile for one or more hostname patterns, and delete one root-folder custom dns rule from a control d profile. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Control D account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Control D capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_ipREADReturn the current IP address and datacenter seen by the Control D API for troubleshooting API token allowed-IP issues.
upsert_profile_ruleWRITECreate or replace root-folder custom DNS rules on a Control D profile for one or more hostname patterns.
INPUTS: profileId / forceOrgId / do / status / hostnames
delete_profile_ruleHIGH IMPACTDelete one root-folder custom DNS rule from a Control D profile.
INPUTS: profileId / ruleId / forceOrgId
get_profileREADFetch one Control D profile by primary key.
INPUTS: profileId / forceOrgId
list_profile_rulesREADList the root-folder custom DNS rules configured on a Control D profile.
INPUTS: profileId / forceOrgId
list_profilesREADList the Control D profiles available to the authenticated API token.
INPUTS: forceOrgId
list_service_categoriesREADList the Control D service categories that can be used for service discovery.
list_services_by_categoryREADList the Control D services available in one service category.
INPUTS: category
INPUT CONTRACTS
Know what the action needs before it runs.
upsert_profile_rule
profileIdREQUIRED- The Control D profile primary key.
forceOrgIdOPTIONAL- Optional child organization ID forwarded as the X-Force-Org-Id header.
doREQUIRED- The Control D rule action code: 0=BLOCK, 1=BYPASS, 2=SPOOF, 3=REDIRECT.
statusOPTIONAL- The Control D rule status code: 0=disabled, 1=enabled.
hostnamesREQUIRED- The hostname patterns to create or update in Control D.
delete_profile_rule
profileIdREQUIRED- The Control D profile primary key.
ruleIdREQUIRED- The Control D rule primary key, usually a hostname or wildcard pattern.
forceOrgIdOPTIONAL- Optional child organization ID forwarded as the X-Force-Org-Id header.
get_profile
profileIdREQUIRED- The Control D profile primary key.
forceOrgIdOPTIONAL- Optional child organization ID forwarded as the X-Force-Org-Id header.
list_profile_rules
profileIdREQUIRED- The Control D profile primary key.
forceOrgIdOPTIONAL- Optional child organization ID forwarded as the X-Force-Org-Id header.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current Ip
Return the current IP address and datacenter seen by the Control D API for troubleshooting API token allowed-IP issues. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_ipControl Upsert Profile Rule
Create or replace root-folder custom DNS rules on a Control D profile for one or more hostname patterns. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
upsert_profile_ruleVerify with Get Profile
Fetch one Control D profile by primary key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_profileSAFETY BOUNDARY
Operate Control D with explicit limits
- Authorize Control D with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_profile_rule` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Control D rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Control D task completed successfully.
CONNECTION MODEL
API key
Control D API token used with the Authorization Bearer header. Create and manage it from the Control D dashboard API page: https://docs.controld.com/docs/org-api
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Control D.