
What happened
Snowflake made per-user AI credit quotas generally available across all CoCo surfaces (Snowsight, CLI, Desktop), and announced three additional governance controls coming soon: organization-wide policy enforcement (MDM), role-based agent profiles, and restricted session scope (RSS) that limits what SQL an agent can execute. The company also introduced Tools by Cortex AI Gateway to centralize and audit external tool access through Model Context Protocol (MCP) servers.
Why it matters
These controls let administrators set spending limits, restrict which external systems agents can reach, and audit all actions without requiring custom code or manual approvals—addressing the security and cost concerns that previously forced teams to sandbox CoCo or limit access. Builders benefit because governance can operate in the background: agent profiles auto-load the right model and skills by role, and approved MCP connections appear automatically, reducing friction while keeping risk bounded.
What to watch
Per-user quotas are available now; MDM, agent profiles, and restricted session scope are generally available soon (the company flags these as forward-looking statements subject to risks). Organizations can query usage details through SNOWFLAKE.ACCOUNT_USAGE or ask CoCo directly which users are consuming the most credits.
Summaries like this, in your inbox every morning.
Snowflake's expansion of CoCo governance reflects a shift in how enterprises approach AI assistants: moving from sandboxing or limiting access to defining clear, enforceable boundaries that let builders operate more freely. The July announcement established three pillars—cost governance, enterprise context, and workplace integration—and today's release operationalizes the first pillar (quotas, now live) while introducing structural controls around access and behavior (coming soon).
The architecture is layered: per-user quotas handle spend; organization-wide policies (MDM), agent profiles, and restricted session scope handle data access and permissions; and Tools by Cortex AI Gateway governs external tool calls. Each control maps to a specific security question an administrator or reviewer might ask. By enforcing these boundaries before a session starts rather than monitoring after the fact, Snowflake positions governance as a prerequisite, not a reaction. This design also reduces friction for builders: approved MCP servers appear automatically, role-based profiles pre-configure the agent, and developers no longer need to manually configure server URLs or manage credentials per service. The result is that governance operates invisibly in the normal case, surfacing only when a user approaches a boundary that would have required approval regardless.
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.
The Motley Fool argues Amazon is the AI company of the two, since AWS was just 21% of first-half 2026 revenue…

Hewlett Packard Enterprise stock is down 5% at $55.87

Anthropic gave six METR staffers hardware, office space and internal tools, putting them roughly on par with i…

Cammarata reinterprets InceptionV1's cat-car neuron as a V-shape detector, not two unrelated concepts

OpenAI is launching the Rosalind Academic Plan, offering eligible research labs at US universities up to 30 fr…

Google Deepmind's Gemini 4 Argon scored 97.5 percent on ARC-AGI-3 at a cost of $4,800, second only to GPT-6 As…
