Skip to main content
Book a demo

Connect DX Data Cloud to Cursor

Give Cursor governed access to DX Data Cloud’s 10 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cursor setup guide

Set up

Add DX Data Cloud to Cursor in four steps

Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.

  1. 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. 2

    Connect Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, DX Data Cloud’s 10 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 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. 4

    Use DX Data Cloud from Cursor

    DX Data Cloud’s approved tools appear in Cursor. Every call is checked against policy and recorded.

Tools

10 DX Data Cloud tools in Cursor

Runlayer policy decides which of these Cursor 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.

See all 10 DX Data Cloud tools

Control

What Runlayer can see and stop in Cursor

Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.

  • Gateway policy (available)

    Every DX Data Cloud call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor 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 Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination