snowflake_get_query_status

Check the status of an asynchronous Snowflake query.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/snowflake-get-query-status.md

WHAT IT DOES

What snowflake_get_query_status does on Integrations MCP

AI agents call snowflake_get_query_status to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why snowflake_get_query_status is rated Low

This is a read-only operation that queries metadata about an existing asynchronous query's status. It has no side effects, does not execute code, and does not modify or delete data. The operation is informational only, making it a Read category tool with low severity.

From the tool's definition Tool name contains 'get' and description states 'Check the status of an asynchronous Snowflake query' — this retrieves query status information without modifying data or executing queries.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs snowflake_get_query_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snowflake_get_query_status, this is the rule to start with:

snowflake_get_query_status Allowed

snowflake_get_query_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "snowflake_get_query_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every snowflake_get_query_status call is checked against it from then on.

FAQ

Questions about snowflake_get_query_status

What does the snowflake_get_query_status tool do? +

Check the status of an asynchronous Snowflake query. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on snowflake_get_query_status? +

Register the Integrations MCP server in PolicyLayer and add a rule for snowflake_get_query_status: 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 Integrations MCP. Nothing to install.

What risk level is snowflake_get_query_status? +

snowflake_get_query_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit snowflake_get_query_status? +

Yes. Add a rate_limit block to the snowflake_get_query_status 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.

How do I block snowflake_get_query_status completely? +

Set action: deny in the PolicyLayer policy for snowflake_get_query_status. 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.

What MCP server provides snowflake_get_query_status? +

snowflake_get_query_status is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →