list_alerts

List Event Management alerts (em_alert) with operational filters. Defaults to alerts that are not Closed, most severe first.

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-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/tedorigawa001-servicenow-mcp/list-alerts.md

WHAT IT DOES

What list_alerts does on ServiceNow-MCP

AI agents call list_alerts to retrieve information from ServiceNow-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 list_alerts is rated Low

Retrieves alert data without side effects; read-only query operation with default filters.

From the tool's definition List Event Management alerts with operational filters, no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_alerts safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_alerts, this is the rule to start with:

list_alerts Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every list_alerts call is checked against it from then on.

FAQ

Questions about list_alerts

What does the list_alerts tool do? +

List Event Management alerts (em_alert) with operational filters. Defaults to alerts that are not Closed, most severe first. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_alerts? +

Register the ServiceNow MCP server in PolicyLayer and add a rule for list_alerts: 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 ServiceNow-MCP. Nothing to install.

What risk level is list_alerts? +

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

Can I rate-limit list_alerts? +

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

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

list_alerts is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ServiceNow, and thousands of servers like it.

This server

All 502 ServiceNow tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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