// SCAN REPORT

Snowflake MCP Server (Read-Only)

6 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 4 Jul 2026

2 can modify or destroy data

4 read-only

6 tools total

Community server · catalogue entry verified 04/07/2026

How to control Snowflake MCP Server (Read-Only) ↓

TOOL MAP

What Snowflake MCP Server (Read-Only) exposes to your agents

Read (4) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Snowflake MCP Server (Read-Only) tools

Execute · High read_query Although described as read-only and limited to SELECT, the tool executes SQL against a live database. Write · Low append_insight This tool creates or appends new entries to an insight memo, which is a reversible modification operation.

2 of Snowflake MCP Server (Read-Only)'s 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Snowflake MCP Server (Read-Only)

PolicyLayer is an MCP gateway — it sits between your AI agents and Snowflake MCP Server (Read-Only), and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "append_insight": {
    "limits": [
      {
        "counter": "append_insight_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "describe_table": {
    "limits": [
      {
        "counter": "describe_table_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Snowflake MCP Server (Read-Only) — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SNOWFLAKE MCP SERVER (READ-ONLY) →

Instant setup, no code required.

FULL CATALOGUE

All 6 Snowflake MCP Server (Read-Only) tools

EXECUTE 1 tools

Execute read_query Execute a SELECT query.

WRITE 1 tools

Write append_insight Add a data insight to the memo

READ 4 tools

Read describe_table Get the schema information for a specific table Read list_databases List all available databases in Snowflake Read list_schemas List all schemas in a database Read list_tables List all tables in a specific database and schema

FAQ

Questions about Snowflake MCP Server (Read-Only)

How do I prevent bulk modifications through Snowflake MCP Server (Read-Only)? +

The Snowflake MCP Server (Read-Only) server has 1 write tools including append_insight. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Snowflake MCP Server (Read-Only).

How many tools does the Snowflake MCP Server (Read-Only) MCP server expose? +

6 tools across 2 categories: Read, Write. 4 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Snowflake MCP Server (Read-Only)? +

Register the Snowflake MCP Server (Read-Only) MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Snowflake MCP Server (Read-Only) tool call.

Deterministic rules across all 6 Snowflake MCP Server (Read-Only) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SNOWFLAKE MCP SERVER (READ-ONLY) →

Instant setup, no code required.

6 Snowflake MCP Server (Read-Only) tools catalogued and risk-classified — across an index of 43,000+ MCP servers.