Skip to main content
Book a demo

Connect Wiz to Cursor

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

Book a demo Cursor setup guide

Set up

Add Wiz to Cursor in four steps

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

  1. 1

    Add Wiz to Runlayer

    Wiz isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  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, Wiz’s 238 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to Wiz

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

  4. 4

    Use Wiz from Cursor

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

Tools

238 Wiz tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • AWS organizations overview

    Run a structured AWS cloud security assessment against a Wiz environment focused on AWS Organization concepts.

  • Code to cloud attack path skill

    Production vulnerability tracing through deployment pipelines to source code and ownership.

  • Cost spike investigation skill

    Cloud cost anomaly investigation for daily, weekly, or monthly spikes.

  • Dev documentation search

    Searches the Wiz Integration Network (WIN) developer documentation (docs.wiz.io/dev) and returns relevant information and links.

  • Devops resource auditing skill

    Security posture assessment for cloud resources experiencing operational anomalies (CPU spikes, memory issues, network anomalies, cost increases).

  • Discover

    Discover available tools organized by domain.

  • Execute

    Execute a tool by name with the given parameters.

  • Execute graph query

    Executes a Wiz Security Graph query using a structured GraphEntityQueryInput JSON object.

See all 238 Wiz 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 Wiz 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