Skip to main content
Book a demo

Connect Power BI to Codex

Give Codex governed access to Power BI’s 4 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Codex setup guide

Set up

Add Power BI to Codex in four steps

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

  1. 1

    Add Power BI to Runlayer

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

    Adding a connector manually
  2. 2

    Connect Codex to Runlayer

    Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Power BI’s 4 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex setup guide
  3. 3

    Sign in to Power BI

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

  4. 4

    Use Power BI from Codex

    Power BI’s approved tools appear in Codex. Every call is checked against policy and recorded.

Tools

4 Power BI tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Execute query

    Executes a DAX query and return the results.

  • Generate query

    Generates a DAX query using the relevant parts of the model schema.

  • Get report metadata

    Retrieves the high-level schema of a Power BI report, including workspace information, semantic model details, pages, visual information, and filters.

  • Get semantic model schema

    Retrieves comprehensive metadata for a specified semantic model, including the serialized schema, custom instructions provided by the model author, and verified answers when available.

Control

What Runlayer can see and stop in Codex

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

  • Gateway policy (available)

    Every Power BI call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Codex 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 or permission request before Codex runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Codex’s model sees it.

  • Redact output in place (not available)

    Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination