NEW: AI Data Reach

Which tool, which table,
for whom and when?

Your agents call tools. Those tools touch data. AI Data Reach tracks the complete round trip — from the user and agent, to the tool and again for the data behind it.

Nested data tables and schemas are applied grants. Arm a role and learn what role is possible — and what comes next.

A Snowflake catalog with its schemas nested inside it. A role is armed, and each schema is annotated with the privilege it holds and whether that privilege was set there or inherited from the catalog above.

Invoking a tool is not the same as reading a table

Tool permissions answer whether an agent may call query. They say nothing about which rows come back. AI Data Reach asks the second question, and asks it on the way through.

  • Tool RBAC decides whether the call is allowed at all
  • AI Data Reach decides whether the data behind it is
  • Both planes — internal and external — call the same gate
  • A denial names the grant that was missing, not just "forbidden"
principalsvc:reporting-bot
toolsnowflake.query allowed
bindingTPCH_SF1.*
objectTPCH_SF1.ORDERS
traversaluse_catalog · inherited
grantselect · analyst · from schema
decisionALLOW

Built for the day after you turn it on

Governance that cannot be inspected, overridden, or recovered from is governance nobody trusts in production.

❄️

Catalog ingest

Point it at a warehouse and the hierarchy arrives on a schedule — catalogs, schemas, and tables, refreshed without a hand-maintained inventory.

🧭

Grants that flow down

A grant on a catalog reaches every schema and table inside it, including ones created later. Drop a deny lower down to carve out the exception.

💬

Answers with reasons

Every decision explains itself in the same sentence the gate used. The screen and the enforcement cannot drift apart, because they call the same function.

🔍

Search that respects access

Filtered through the resolver, so results never reveal an object the searcher cannot reach — and ranked to surface denies and credential-vending grants first.

🏷️

Per-tenant enforcement

Each namespace can run in observe or enforce mode. Turning enforcement off takes platform admin — a tenant cannot switch off its own governance.

🚪

Break-glass and recovery

Objects whose owner no longer resolves can be claimed by an admin, recorded as break-glass. Nothing is permanently unadministrable.

Where catalogs come from

Snowflake is available today. The rest are in progress — listed here rather than implied, so you can tell which is which.

Snowflake — available BigQuery — in progress Databricks — in progress AWS Glue — in progress

Find out what your
agents can reach.

Point AI Data Reach at a warehouse and see the graph against your own catalog.

Schedule a Demo → View on GitHub →