Skip to main content
Book a demo

Connect Sigma to Crush

Give Crush governed access to Sigma’s 7 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Crush setup guide

Set up

Add Sigma to Crush in four steps

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

  1. 1

    Add Sigma to Runlayer

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

    Adding a connector manually
  2. 2

    Connect Crush to Runlayer

    Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Sigma’s 7 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Crush setup guide
  3. 3

    Sign in to Sigma

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

  4. 4

    Use Sigma from Crush

    Sigma’s approved tools appear in Crush. Every call is checked against policy and recorded.

Tools

7 Sigma tools in Crush

Runlayer policy decides which of these Crush users can call.

  • Begin session

    REQUIRED — You MUST call this tool before using any other Sigma tool in a conversation.

  • Call agent

    Call a Sigma workbook agent with a message or conversation.

  • Describe

    Inspect the schema of a Sigma data source.

  • List documents

    Browse a named document collection in the Sigma workspace.

  • List workbook agents

    List the workbook agents you can edit across your organization

  • Query

    Execute a SQL query against a Sigma data source and return the results.

  • Search

    Search across the entire Sigma workspace to discover workbooks, data models, data model elements, and tables.

Control

What Runlayer can see and stop in Crush

Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.

  • Gateway policy (available)

    Every Sigma call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination