Skip to main content
Book a demo

Connect Drata to Cursor

Give Cursor governed access to Drata’s 38 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cursor setup guide

Set up

Add Drata to Cursor in four steps

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

  1. 1

    Approve Drata in Runlayer

    Add Drata 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, Drata’s 38 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to Drata

    Sign in the way Drata requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Drata from Cursor

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

Tools

38 Drata tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • Create background check

    File a Background Check for a personnel record, evidenced by a URL.

  • Create control

    Create a new compliance control in a workspace.

  • Create evidence

    Register a new evidence bucket in Drata's reusable Evidence Library.

  • Create risk

    Create a new custom risk in a risk register.

  • Create vendor

    Create a new third-party vendor for the account (TPRM).

  • Delete evidence

    Permanently delete an ENTIRE evidence bucket -- the folder AND every file in it, plus all version history and control linkages.

  • Delete evidence artifact

    Permanently delete ONE file from an evidence bucket, including that file's entire version history.

  • Delete risk

    Permanently delete a single risk from a risk register.

See all 38 Drata 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 Drata 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