snowflake_get_query_history

A read tool on the Integrations MCP server.

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-history.md

WHAT IT DOES

What snowflake_get_query_history does on Integrations MCP

AI agents call snowflake_get_query_history 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_history is rated Low

The 'get_' prefix and 'query_history' context suggest this tool retrieves historical query data from Snowflake without modifying it. However, confidence is reduced to 0.75 rather than higher because: (1) the description is empty, preventing confirmation of exact behavior; (2) query history access could expose sensitive information about database operations, warranting medium severity; (3) there is a possibility it…

From the tool's definition Tool name contains 'get_query_history' which indicates a read/retrieval operation. The name structure follows the 'Read' pattern of get/list/fetch tools seen in sibling tools (e.g., airtable_get_record, amplitude_get_event_counts).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs snowflake_get_query_history 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_history, this is the rule to start with:

snowflake_get_query_history Allowed

snowflake_get_query_history 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_history": {}
  }
}

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_history call is checked against it from then on.

FAQ

Questions about snowflake_get_query_history

What does the snowflake_get_query_history tool do? +

snowflake_get_query_history is a read tool on the Integrations MCP server. 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_history? +

Register the Integrations MCP server in PolicyLayer and add a rule for snowflake_get_query_history: 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_history? +

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

Can I rate-limit snowflake_get_query_history? +

Yes. Add a rate_limit block to the snowflake_get_query_history 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_history completely? +

Set action: deny in the PolicyLayer policy for snowflake_get_query_history. 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_history? +

snowflake_get_query_history 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_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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