resolve_incident · ServiceNow MCP Server MCP: Risk & Policy

WHAT IT DOES

What resolve_incident does on ServiceNow MCP Server

AI agents use resolve_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 IT NEEDS A POLICY

Why resolve_incident needs a policy

Resolving an incident updates its status field in ServiceNow, modifying data in a way that is reversible (incidents can be reopened). This falls under Write category. Severity is medium because unauthorized incident resolution could disrupt incident tracking, mask ongoing issues, and mislead stakeholders about service status, but does not cause permanent data loss or financial impact.

From the tool's definition Tool name 'resolve_incident' and description 'Resolve an incident in ServiceNow' indicates modification of incident state/status, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_incident Rate-limited

resolve_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_incident": {
      "limits": [
        {
          "counter": "resolve_incident_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ServiceNow MCP Server, so you can run agents against it safely.

FAQ

Questions about resolve_incident

What does the resolve_incident tool do? +

Resolve an incident in ServiceNow. 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.

How do I enforce a policy on resolve_incident? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for resolve_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.

What risk level is resolve_incident? +

resolve_incident is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resolve_incident? +

Yes. Add a rate_limit block to the resolve_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.

How do I block resolve_incident completely? +

Set action: deny in the PolicyLayer policy for resolve_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.

What MCP server provides resolve_incident? +

resolve_incident is provided by the ServiceNow MCP Server MCP server (shameerampcome/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.