get_alert_summary
Operational overview of open alerts: counts by severity, by state, acknowledged vs not, and the top sources. Read-only.
This record as markdown: /tools/tedorigawa001-servicenow-mcp/get-alert-summary.md
What get_alert_summary does on ServiceNow-MCP
AI agents call get_alert_summary 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.
Why get_alert_summary is rated Low
Tool retrieves alert statistics and summaries without modifying or executing operations.
From the tool's definition Operational overview of open alerts, read-only.
Attacks that exploit this kind of access
The rule that runs get_alert_summary 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 get_alert_summary, this is the rule to start with:
get_alert_summary is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every get_alert_summary call is checked against it from then on.
Questions about get_alert_summary
Operational overview of open alerts: counts by severity, by state, acknowledged vs not, and the top sources. Read-only. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP server in PolicyLayer and add a rule for get_alert_summary: 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.
get_alert_summary 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 get_alert_summary 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 get_alert_summary. 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.
get_alert_summary 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.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue