---
title: "Data context and governance: posts and guides | Rig"
description: "Semantic and context layers tell people and AI agents what the data means, MCP connects their tools, and Gateway decides what each of them may query."
canonical: "https://rig.so/blog/data-context"
format: markdown
---

[Blog](https://rig.so/blog)

# Data context and governance

Semantic and context layers tell people and AI agents what the data means, MCP connects their tools, and Gateway decides what each of them may query.

[Data context and governance](https://rig.so/use-cases/data-context-and-governance)

[Data context and governanceAn AI policy PDF has never stopped a queryAn AI governance framework for data access sets out who, and which agents, can query which data, under which policy, and how every query is logged.Read](https://rig.so/blog/ai-governance-framework-for-data-access)[Data context and governanceAn MCP gateway is how you stop a server being a free-for-allAn MCP gateway is a control point in front of your warehouse. Each person and agent gets a role, a token and a log in place of a shared database password.Read](https://rig.so/blog/what-is-an-mcp-gateway)[Data context and governanceCan we stop calling a chatbot on raw tables a company brain?A company brain is a governed map of your company data that staff and AI agents can ask, built on the warehouse you already run. Here is the build order.Read](https://rig.so/blog/how-to-build-a-company-brain)[Data context and governanceEveryone's banging on about context, but what actually is it?A context layer is a navigational map of systems, metric definitions and business meanings. The facts on a deal belong in the warehouse, away from memory files.Read](https://rig.so/blog/what-actually-is-context)[Data context and governanceHorizon and Unity Catalog still won’t tell you which agent ran the queryHow Snowflake Horizon, Unity Catalog, BigQuery and Fabric with Purview control what AI agents can query, and what a gateway adds when agents share a login.Read](https://rig.so/blog/warehouse-governance-for-ai-agents)[Data context and governanceHow far do Snowflake Semantic Views actually get you?Snowflake semantic views keep metrics, dimensions and relationships in the database under normal RBAC. Agents still need a context layer and their own access.Read](https://rig.so/blog/snowflake-context-layer-and-semantic-views)[Data context and governanceI wouldn't let an agent loose on a Databricks metric view and nothing elseDatabricks metric views give you a semantic layer in Unity Catalog. Here is what they cover, and what agents still need: a role, row limits and a log.Read](https://rig.so/blog/databricks-context-layer-and-metric-views)[Data context and governanceI'd stop treating a Power BI model like the company brainA Power BI semantic model is built for Power BI reports. Keep shared metrics in a warehouse semantic layer so other tools and AI agents use the same definitions.Read](https://rig.so/blog/power-bi-semantic-model-vs-warehouse-semantic-layer)[Data context and governanceIf dbt holds the metrics, who decides who can query them?dbt keeps metrics in your project; Snowflake semantic views and Databricks metric views keep them in the engine. Neither alone decides which agent may query them.Read](https://rig.so/blog/dbt-semantic-layer-vs-warehouse-native-semantic-views)[Data context and governanceNobody needs the whole enterprise context layer on day oneBuild an enterprise context layer one domain at a time, from a table inventory and agreed metrics to ownership, access and a gateway for agents.Read](https://rig.so/blog/how-to-build-an-enterprise-context-layer)[Data context and governancePlease stop giving agents the warehouse passwordAn MCP server exposes tools and data to AI clients. For a warehouse, run each call as a named agent, against certified metrics, with a log of every call.Read](https://rig.so/blog/what-is-an-mcp-server)[Data context and governancePointing Genie at raw tables is a fun way to get confident wrong answersGenie answers well when metrics live in Unity Catalog metric views and each caller sees only their rows. This guide covers the setup, from metric views to access.Read](https://rig.so/blog/databricks-genie-semantic-layer)[Data context and governanceSemantics, ontology, context... buzzword bingo, or business value?Semantic layer, ontology, context layer and knowledge graph are four different things. An agent needs the first three to find the agreed number.Read](https://rig.so/blog/semantics-ontology-context-buzzword-bingo)[Data context and governanceThe metrics should not be hiding in the ingest toolELT loads data into the warehouse first and transforms it there, while ETL transforms it before load. When to use each, and where metric definitions belong.Read](https://rig.so/blog/elt-vs-etl)[Migration guideWhere do the metrics live once Fivetran is gone?Inventory every connector and schedule, stand up the replacement ingest, run both until the row counts match, then cut over. Metrics belong in the warehouse.Read](https://rig.so/blog/fivetran-migration-guide)[Data context and governanceWho is Claude logged in as, once you've connected it to Snowflake?Connect Claude, ChatGPT or Cursor to Snowflake, BigQuery or Databricks over MCP, with certified metrics, a role for each agent and a log of every query.Read](https://rig.so/blog/how-to-connect-ai-agents-to-your-data-warehouse)[Data context and governanceWTF is a semantic layer anyway?A semantic layer is a dictionary of definitions for business numbers. Each BI tool used to keep its own, in a format agents could not read. Apache Ossie opens it up.Read](https://rig.so/blog/wtf-is-a-semantic-layer)

Talk to Rig

## See your stack drawn as one diagram

An architect drafts a one-page diagram of your warehouse, sources and access path, then offers a 30-minute walkthrough.

[Request an architecture diagram for your stack](https://rig.so/book-demo?offer=architecture_diagram&from=%2Fblog%2Fdata-context)[Book a call with an architect](https://rig.so/book-demo?offer=architect_call&from=%2Fblog%2Fdata-context)

---

- [This page as HTML](https://rig.so/blog/data-context)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)
