
What happened
Snowflake is rolling out per-user AI credit quotas (now generally available) and three new governance layers (generally available soon)—organization-wide policy management, team-level agent profiles, and restricted session scope—that let administrators set spending limits, control which external tools agents can access, and constrain SQL permissions before a session starts.
Why it matters
Platform and security teams can now approve broader access to CoCo across their organizations instead of confining it to sandboxes or manual approval workflows. The controls map to specific security review questions: spend bounds, policy consistency across surfaces, explicit data reach, and logged external tool access. Developers inherit these guardrails automatically without extra configuration work.
What to watch
Tools by Cortex AI Gateway (preview soon) centralizes MCP server governance and adds four controls that did not previously exist—server-level allowlisting, tool-level policy, per-server rate limits, and comprehensive audit trails of tool calls. Per-user quotas reset daily and monthly independently, preventing unexpected end-of-month charges and enforcing spending ceilings across CoCo in Snowsight, CoCo CLI, and CoCo Desktop.
Summaries like this, in your inbox every morning.
Snowflake's announcement builds on a July blog post about scaling enterprise AI with trust, structured around three themes: managing costs, grounding AI in enterprise context, and embedding AI into existing workflows. Today's expansion addresses a core tension in enterprise AI adoption: teams want broad developer access to AI agents for productivity gains, but security and platform teams need visibility and control to manage risk. The new controls answer this by distributing governance across four dimensions—cost, data reach, behavior, and external integrations—each enforced at session initiation rather than monitored after the fact.
Per-user quotas are the first and simplest control, now live across all CoCo surfaces. The three additional layers tackle governance depth: organization-wide policy (MDM) ensures consistent rules whether developers use the web interface, CLI, or desktop; agent profiles handle role-based defaults without per-developer setup; restricted session scope (RSS) directly answers the "blast radius" question by constraining an agent to SQL permissions tied to active roles, not implicit user credentials. The introduction of Tools by Cortex AI Gateway—built on technology from the Natoma acquisition—signals a strategic pivot toward centralized, auditable external tool governance, addressing a gap where teams previously had few controls over MCP server access.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Chunghwa Telecom president Rong-shy Lin said the shift from conversational AI to autonomous AI agents is resha…

CoreWeave fell 5% in premarket trading Friday and was on track to finish the week down 15%, after rebounding f…

Apple and Meta said they would jointly release a new open-weight AI model designed to run on high-end Macs, ai…

Investors put $38.5 billion into Asian startups in Q3, per Crunchbase data

A writer and entrepreneur opened his daily to-do list and found 156 items, and concluded that an AI assistant…

A longtime Anthropic investor told Fortune he expects shares priced around $1.8 trillion, below the company's…
