servicenow_get_incident
Get full details of a specific ServiceNow incident by number or sys_id.
This record as markdown: /tools/com-local-mcp-local-mcp/servicenow-get-incident.md
What servicenow_get_incident does on Local
AI agents call servicenow_get_incident 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 |
|---|---|---|---|
id | string | Yes | Incident number (e.g. 'INC0012345') or sys_id |
Parameters from the server's own tool schema.
Why servicenow_get_incident is rated Low
This tool retrieves incident information from ServiceNow without creating, modifying, deleting, or executing any operations. It is a straightforward data query operation. The severity is low because read operations have minimal blast radius — the worst outcome would be unauthorized information disclosure of incident details, but no system state is altered.
From the tool's definition Tool description states 'Get full details of a specific ServiceNow incident' — the verb 'Get' and phrase 'full details' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs servicenow_get_incident 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_get_incident, this is the rule to start with:
servicenow_get_incident 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_get_incident call is checked against it from then on.
Questions about servicenow_get_incident
Get full details of a specific ServiceNow incident by number or sys_id. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
servicenow_get_incident accepts 1 parameter: id. Required: id. 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_get_incident: 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_get_incident 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_get_incident 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_get_incident. 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_get_incident 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