Skip to main content
Book a demo

Connect Box to Cursor

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

Book a demo Cursor setup guide

Set up

Add Box to Cursor in four steps

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

  1. 1

    Approve Box in Runlayer

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

    Cursor setup guide
  3. 3

    Sign in to Box

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

  4. 4

    Use Box from Cursor

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

Tools

35 Box tools in Cursor

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

  • Add items to hub

    Adds files, folders, or web links to a specific hub, enabling content organization within collaborative workspaces.

  • Copy file

    Copies an existing file to a destination folder in Box (see Box API Copy file).

  • Copy folder

    Copies an existing folder to a destination parent folder in Box (see Box API Copy folder).

  • Copy hub

    Creates a copy of an existing Box Hub via the Hubs v3 API (POST /v3/hubs/{id}:copy).

  • Create file comment

    Creates a new comment on a specific file.

  • Create folder

    Creates new folders in Box.

  • Create hub

    Creates new collaborative hubs for organizing content around specific topics, projects, or teams.

  • Create metadata template

    Creates a new enterprise metadata template.

See all 35 Box 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 Box 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