snowflake_get_query_history
AI agents call snowflake_get_query_history to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
snowflake_get_query_history. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
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.
snowflake_get_query_history 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 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.
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.
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.
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 →