Back to Devoured - November 12, 2026
DEVOURED
Who is actually using your Snowflake MCP server?

Who is actually using your Snowflake MCP server?

Data Medium
Snowflake's default query logging makes it difficult to audit AI-driven activity, but individual OAuth integrations for MCP servers provide the necessary visibility.
What: By assigning each Model Context Protocol (MCP) server its own OAuth integration, administrators can differentiate between human users and AI agents in Snowflake query logs. Joining login history with query history enables tracking per-server usage.
Why it matters: As enterprises begin using AI agents to interact with their data warehouses, standard audit logs become noisy and insufficient for security governance without explicit identity attribution per agent.
Takeaway: If you have deployed MCP servers connected to Snowflake, implement separate OAuth security integrations for each server to enable granular audit logging.
Decoder
  • Model Context Protocol (MCP): A standard for connecting AI assistants to data sources and tools.
  • Snowsight: Snowflake's web-based user interface for managing and querying data.
Original article

Snowflake's query history cannot tell a Snowsight query from the same SQL sent by Claude through an MCP server. This post presents a fix that gives each MCP server its own OAuth security integration, then joins query history to login history on one column to get usage per server, user, and day. It also covers where the approach stops working.

Explore all 61 articles in today's digest

Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi