Low Risk

list_recent_incidents

Fetches a list of the most recently created incidents.

How to control list_recent_incidents ↓

What list_recent_incidents does on Snow

AI agents call list_recent_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.

Low Risk

Why list_recent_incidents needs a policy

This tool performs a query operation to retrieve incident data from ServiceNow without side effects. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could retrieve incident information but cannot take consequential actions with this tool alone.

From the tool's definition Tool name 'list_recent_incidents' and description 'Fetches a list of the most recently created incidents' indicate data retrieval with no modification or execution.

Documented attack patterns abuse exactly the kind of access list_recent_incidents gives an agent:

How to control list_recent_incidents

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_recent_incidents:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_recent_incidents": {}
  }
}

list_recent_incidents is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Snow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_recent_incidents

What does the list_recent_incidents tool do? +

Fetches a list of the most recently created incidents. It is categorised as a Read tool in the Snow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_recent_incidents? +

Register the Snow MCP server in PolicyLayer and add a rule for list_recent_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.

What risk level is list_recent_incidents? +

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

Can I rate-limit list_recent_incidents? +

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

How do I block list_recent_incidents completely? +

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

What MCP server provides list_recent_incidents? +

list_recent_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.

Enforce policy on every Snow tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.