categorize_incident
Use Predictive Intelligence to predict category, assignment group, and priority (latest release: LightGBM algorithm)
This record as markdown: /tools/servicenow-mcp-server/categorize-incident.md
What categorize_incident does on ServiceNow MCP Server
AI agents use categorize_incident to create or update resources in ServiceNow MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.
Why categorize_incident is rated Medium
While framed as 'prediction', this tool likely writes/updates incident fields (category, assignment group, priority) on a ServiceNow record using Predictive Intelligence. Modifying these fields constitutes a reversible data write. It doesn't delete data, execute arbitrary code, or involve finances.
From the tool's definition 'predict category, assignment group, and priority' — the tool applies ML predictions to set fields on an incident record
Attacks that exploit this kind of access
The rule that runs categorize_incident safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For categorize_incident, this is the rule to start with:
categorize_incident stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every categorize_incident call is checked against it from then on.
Questions about categorize_incident
Use Predictive Intelligence to predict category, assignment group, and priority (latest release: LightGBM algorithm). It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for categorize_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 ServiceNow MCP Server. Nothing to install.
categorize_incident is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the categorize_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 categorize_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.
categorize_incident is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue