Search for incidents
AI agents call incident_search to retrieve information from ServiceNow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search/query operation to retrieve incident information from ServiceNow. Search operations are read-only and have no side effects—they do not create, modify, delete, or execute any changes to the ServiceNow instance. The blast radius of misuse is minimal, limited to potential information disclosure of incident data that an agent might already have access to.
From the tool's definition Tool name 'incident_search' and description 'Search for incidents' indicate a query operation that retrieves incident data without modifying or deleting any records.
Attacks that exploit this kind of access
Search for incidents. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for incident_search: 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 Server. Nothing to install.
incident_search 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 incident_search 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 incident_search. 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.
incident_search is provided by the ServiceNow MCP Server MCP server (lokimcpuniverse/servicenow-mcp-server). 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 →