Snowflake Key Pair Auth connector for AI agents

Snowflake Key Pair Auth tools for AI agents

CALL ANY TOOL

12 tools covering get, execute, cancel.

snowflakekeyauth_cancel_query

Cancel a running snowflake sql api statement by statement ha

Cancel a running snowflake sql api statement by statement handle.

Parameters

Name

Type

Required

Description

statement_handle

string

Required

Snowflake statement handle to cancel

request_id

string

Optional

Optional request ID used when the statement was submitted

snowflakekeyauth_execute_query

Execute one or more sql statements against snowflake using t

snowflakekeyauth_get_columns

Query information_schema.columns for column metadata.

snowflakekeyauth_get_query_partition

Get a specific result partition for a snowflake sql api stat

snowflakekeyauth_get_query_status

Get snowflake sql api statement status and first partition r

snowflakekeyauth_get_referential_constraints

Query information_schema.referential_constraints.

snowflakekeyauth_get_schemata

Query information_schema.schemata for schema metadata.

snowflakekeyauth_get_table_constraints

Query information_schema.table_constraints.

snowflakekeyauth_get_tables

Query information_schema.tables for table metadata in a snow

snowflakekeyauth_show_databases_schemas

Run show databases or show schemas.

snowflakekeyauth_show_grants

Run show grants in common modes (to role, to user, of role,

snowflakekeyauth_show_imported_exported_keys

Run show imported keys or show exported keys for a table. fo

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="snowflakekeyauth")

mcp = MultiServerMCPClient({
    "snowflakekeyauth": {
        "url": "https://mcp.scalekit.com/snowflakekeyauth",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "snowflakekeyauth" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/snowflakekeyauth
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "snowflakekeyauth" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/snowflakekeyauth
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="snowflakekeyauth")
# Connect to MCP at https://mcp.scalekit.com/snowflakekeyauth
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Get started

Run SHOW WAREHOUSES?

Run SHOW PRIMARY KEYS with optional scope?

Advanced

Copy the prompt

Copied

Run SHOW GRANTS in common modes (to role, to user, of role, on object)?

Copy the prompt

Copied

Run SHOW DATABASES or SHOW SCHEMAS?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Snowflake Key Pair Auth

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Snowflake Key Pair Auth

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Snowflake Key Pair Auth

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Snowflake Key Pair Auth

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

SALES

Deal intelligence agent

Combine Gong, Attio, and Slack signals to surface deal risks and next-best actions. Updated after every call.

ENGINEERING

Engineering standup agent

Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Snowflake Key Pair Auth as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Snowflake Key Pair Auth bearer token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Snowflake Key Pair Auth?
Yes. Pass a tool name filter to listScopedTools so the analytics agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Snowflake Key Pair Auth.

What happens when a user revokes Snowflake Key Pair Auth access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does query execution respect Snowflake role-based access?
Yes. Queries run under the connected key pair's Snowflake role, with row access policies and masking intact. Scalekit vaults the private key and adds per-call scope checks and audit on top.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit