Check the status of an asynchronous Snowflake query.
AI agents call snowflake_get_query_status 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.
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
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.
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.
snowflake_get_query_status 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_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.
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.
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.
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 →