servicenow_list_my_incidents
List incidents assigned to you or opened by you in ServiceNow.
This record as markdown: /tools/com-local-mcp-local-mcp/servicenow-list-my-incidents.md
What servicenow_list_my_incidents does on Local
AI agents call servicenow_list_my_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 20, max 50) |
state | string | — | Filter by state: 'open' (default), 'resolved', 'all' |
Parameters from the server's own tool schema.
Why servicenow_list_my_incidents is rated Low
The tool retrieves and displays incident data from ServiceNow without creating, modifying, deleting, or executing any operations. It is purely informational with minimal blast radius if misused by an AI agent (would only retrieve existing incident information the user is already authorized to access).
From the tool's definition Tool name uses 'list' verb and description states 'List incidents assigned to you or opened by you in ServiceNow' — this is a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs servicenow_list_my_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_list_my_incidents, this is the rule to start with:
servicenow_list_my_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_list_my_incidents call is checked against it from then on.
Questions about servicenow_list_my_incidents
List incidents assigned to you or opened by you in ServiceNow. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
servicenow_list_my_incidents accepts 2 parameters: limit, state. 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_list_my_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_list_my_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_list_my_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_list_my_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_list_my_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