servicenow_search_incidents
Search incidents in ServiceNow by keyword, number, or caller.
This record as markdown: /tools/com-local-mcp-local-mcp/servicenow-search-incidents.md
What servicenow_search_incidents does on Local
AI agents call servicenow_search_incidents to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max results (default 10, max 50) |
query | string | Yes | Free-text search or incident number (e.g. 'INC0012345' or 'printer not working') |
Parameters from the server's own tool schema.
Why servicenow_search_incidents is rated Low
This tool retrieves or queries incident data from ServiceNow without creating, modifying, deleting, or executing any actions. The search functionality is a read-only operation. Severity is low because the blast radius of misuse is limited to information disclosure of potentially sensitive incident data, which while concerning, does not enable destructive, financial, or code execution risks.
From the tool's definition Tool name contains 'search' and description states 'Search incidents in ServiceNow by keyword, number, or caller' — these are query/retrieval operations with no modification or execution of external systems.
Attacks that exploit this kind of access
The rule that runs servicenow_search_incidents safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For servicenow_search_incidents, this is the rule to start with:
servicenow_search_incidents 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 Local, apply this rule, and every servicenow_search_incidents call is checked against it from then on.
Questions about servicenow_search_incidents
Search incidents in ServiceNow by keyword, number, or caller. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
servicenow_search_incidents accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for servicenow_search_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 Local. Nothing to install.
servicenow_search_incidents 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 servicenow_search_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.
Set action: deny in the PolicyLayer policy for servicenow_search_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.
servicenow_search_incidents is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue