Skip to main content
Book a demo

Connect Lattice to Cursor

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

Book a demo Cursor setup guide

Set up

Add Lattice to Cursor in four steps

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

  1. 1

    Approve Lattice in Runlayer

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

    Cursor setup guide
  3. 3

    Sign in to Lattice

    Each user signs in to Lattice with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Lattice from Cursor

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

Tools

22 Lattice tools in Cursor

Runlayer policy decides which of these Cursor users can call. 15 read data only.

  • Find ancestors

    Find ancestors.

  • Find employees

    Searches for employees in the user's company by name, work email, and/or department.

  • Find feedback

    Retrieves feedback items the user has visibility into.

  • Find one on ones

    Find one on ones.

  • Find reports

    Find reports.

  • Find reviews

    Retrieves reviews the user is permitted to see, filterable by who the review is about, who wrote it, the cycle, direction, submission/sharing status, and date range.

  • Get current update draft

    Returns the user's current-period update draft, with the questions on the form, any answers already saved, the period bounds, and the cadence.

  • Get draft reviews

    Retrieves the open performance review drafts the user is currently authoring.

See all 22 Lattice 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 Lattice 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