Lists incidents based on a query, with support for pagination and field selection.
AI agents call list_incidents to retrieve information from Snow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward read operation that queries and returns incident data without modifying, deleting, or executing any external actions. The inclusion of pagination and field selection are standard query filtering features that do not alter data. No permission checks, approvals, or state changes are implied.
From the tool's definition Tool name 'list_incidents' and description explicitly states it 'Lists incidents based on a query, with support for pagination and field selection.' The verb 'Lists' and the retrieval-focused functionality with query/pagination/field selection parameters…
Documented attack patterns abuse exactly the kind of access list_incidents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Snow, and nothing reaches the server without passing your rules. This is the rule we recommend for list_incidents:
{
"version": "1",
"default": "deny",
"tools": {
"list_incidents": {}
}
}list_incidents is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists incidents based on a query, with support for pagination and field selection. It is categorised as a Read tool in the Snow MCP Server, which means it retrieves data without modifying state.
Register the Snow MCP server in PolicyLayer and add a rule for list_incidents: 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 Snow. Nothing to install.
list_incidents 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 list_incidents 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 list_incidents. 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.
list_incidents is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Snow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
88 Snow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.