Test the Snowflake connection and return basic account information
AI agents call test_snowflake_connection to retrieve information from Snowflake Developer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves connection status and account metadata. It does not create, modify, delete, or execute operations. The blast radius of misuse is minimal—at worst an attacker learns basic account info already available to authenticated users. Given the context of a Snowflake admin tool, basic account information is non-sensitive metadata (account name, region, version).
From the tool's definition Tool name 'test_snowflake_connection' and description states it tests connection and returns 'basic account information' — a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Test the Snowflake connection and return basic account information. It is categorised as a Read tool in the Snowflake Developer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Snowflake Developer MCP Server MCP server in PolicyLayer and add a rule for test_snowflake_connection: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Snowflake Developer MCP Server. Nothing to install.
test_snowflake_connection is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the test_snowflake_connection rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for test_snowflake_connection. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
test_snowflake_connection is provided by the Snowflake Developer MCP Server MCP server (mcp-tg/snowflake-developer-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →