Connect DX Data Cloud to Cline CLI
Give Cline CLI governed access to DX Data Cloud’s 10 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add DX Data Cloud to Cline CLI in four steps
Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.
- 1
Approve DX Data Cloud in Runlayer
Add DX Data Cloud from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Cline CLI to Runlayer
Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches DX Data Cloud’s 10 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Cline CLI setup guide - 3
Sign in to DX Data Cloud
An admin adds DX Data Cloud credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use DX Data Cloud from Cline CLI
DX Data Cloud’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.
Tools
10 DX Data Cloud tools in Cline CLI
Runlayer policy decides which of these Cline CLI users can call.
Get entity details
Get comprehensive details about a specific entity including its information, tasks, and scorecards - we can use this to check operational readiness/health of an entity.
Get initiative details
Get initiative details including both the initiative info and its progress report.
Get scorecard info
Retrieve details about a specific scorecard, including its defined levels and checks.
Get team details
Retrieve details for an individual team.
List entities
List entities from the DX software catalog.
List initiatives
Lists all initiatives with summary information.
List scorecards
List all active scorecards.
List teams
List all teams in DX.
Control
What Runlayer can see and stop in Cline CLI
Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.
Gateway policy (available)
Every DX Data Cloud call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Cline CLI as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Cline CLI runs it.
Block output after it runs (not available)
Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.
In Cline CLI
- If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
- This covers the Cline CLI, not the Cline extension for VS Code.
Frequently asked questions
Connect more
