Connect Snowflake to Hermes
Give Hermes governed access to Snowflake’s 8 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Snowflake to Hermes in four steps
Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.
- 1
Approve Snowflake in Runlayer
Add Snowflake from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Hermes to Runlayer
Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches Snowflake’s 8 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Hermes setup guide - 3
Sign in to Snowflake
Each user signs in to Snowflake with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Snowflake from Hermes
Snowflake’s approved tools appear in Hermes. Every call is checked against policy and recorded.
Tools
8 Snowflake tools in Hermes
Runlayer policy decides which of these Hermes users can call.
Describe semantic view
Describe a semantic view.
Get semantic view ddl
Get the DDL for a semantic view.
List semantic views
List all semantic views in the account, database, or schema.
Query semantic view
Writes and runs a statement to query a semantic view using DIMENSIONS, METRICS, and/or FACTS.
Run Snowflake query
Run a SQL query in Snowflake.
Show semantic dimensions
Show all semantic dimensions in the account, database, or schema.
Show semantic metrics
Show all semantic metrics in the account, database, or schema.
Write semantic view query tool
Writes a query statement to query a semantic view using DIMENSIONS, METRICS, and/or FACTS.
Control
What Runlayer can see and stop in Hermes
Some controls apply to every client at the gateway. Others depend on what Hermes exposes to Runlayer.
Gateway policy (available)
Every Snowflake call from Hermes passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Hermes as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Hermes runs it.
Block output after it runs (available)
Runlayer can block a tool’s output in Hermes and show a message in its place.
Redact output in place (not available)
Hermes cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
In Hermes
- Hermes can replace blocked tool output with a message, but its after-call event is for monitoring only.
Frequently asked questions
Connect more
