Semantic AI-powered search across KB, catalog, incidents (ServiceNow AI Search)
AI agents call ai_search to retrieve information from ServiceNow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves or queries data from ServiceNow knowledge bases, catalogs, and incident records without any side effects. It does not create, modify, delete, or execute external operations. The low severity reflects minimal blast radius—misuse would only retrieve information the agent might not be authorized to see, but cannot alter system state or trigger unintended actions.
From the tool's definition Tool performs semantic AI-powered search across KB, catalog, and incidents. The description uses search and query terminology ('search across') with no mention of modification, execution, deletion, or financial operations.
Attacks that exploit this kind of access
Semantic AI-powered search across KB, catalog, incidents (ServiceNow AI Search). 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 ai_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. Nothing to install.
ai_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 ai_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 ai_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.
ai_search 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.
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 →