> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Wiz

> Give the Sazabi agent read-only access to the Wiz Security Graph for cloud exposure, attack paths, vulnerabilities, and runtime threat context.

[All Wiz integration capabilities](https://docs.sazabi.com/catalogs/integrations/wiz)

## About

This is an MCP connector that gives the Sazabi agent tools from Wiz's hosted MCP server (`mcp.app.wiz.io`). Wiz authenticates over OAuth with dynamic client registration, and the server reads the Wiz Security Graph as the Wiz user who connects it.

Sazabi connects read-only. It requests Wiz's read scope and never the scope that lets the server file findings, and Wiz tools that change state (remediation, issue status, policies and rules) are blocked and cannot be called. The agent can investigate your environment but cannot change anything in Wiz.

Use it to add cloud exposure and runtime context to a GuardDuty, CloudTrail, Kubernetes, or WAF signal: the logs show what happened, and Wiz shows how exposed the resource is and what an attacker could reach from it.

**What the agent can do:**

* Look up the cloud resource named in a security signal and see the issues open on it
* Check whether a resource is exposed to the internet and what sensitive data or privileged identities it can reach
* Read vulnerabilities, threats, and ownership for an instance, container image, cluster, or workload

## Prerequisites

* A Wiz tenant with the Wiz MCP integration enabled. A Wiz user who can manage integrations enables it from the Wiz integration portal.
* A Wiz account that can view the data the agent needs. The connector reads no more than that user can see.

## Set up in the dashboard

Configure connectors in the dashboard under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 1**

### Open the connector

Find Wiz in [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 2**

### Authorize

Start the connection. Sazabi redirects you to Wiz, where you sign in with your Wiz account and approve access, then back.

## Set up with the CLI

You can also connect Wiz with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [`sazabi mcp-connectors` reference](https://docs.sazabi.com/reference/cli/mcp-connectors)).

Wiz authenticates over OAuth, so the CLI opens a browser to complete authorization:

```bash theme={"system"}
sazabi mcp-connectors connect wiz
```

Add `--project-id <project>` to target a specific project, or `--no-wait` to print the authorization link and exit without waiting. With `--json` the command prints the authorization URL and returns without waiting. Confirm the result with `sazabi mcp-connectors list`.

## Verify

Open the connector's connection page under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors) and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to list the open Wiz issues on one of your cloud resources and confirm it returns them.

## Troubleshooting

**Wiz sign-in succeeds but no tools are discovered** — The Wiz MCP integration is probably not enabled for your tenant. Ask a Wiz user who can manage integrations to enable it from the Wiz integration portal, then reconnect from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**A lookup returns an authorization error** — The Wiz user who connected the server cannot see that data. Reconnect with a user who can.

**Connection shows needs attention** — The authorization may have expired or been revoked; reconnect from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

## Further reading

> [card] [Agent tools](https://docs.sazabi.com/guides/investigate/agent-tools.md)
>
> How the agent uses connector tools.

> [card] [MCP connectors](https://docs.sazabi.com/catalogs/mcp-connectors.md)
>
> Browse the connector catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.