close_incident

Close a resolved incident (requires WRITE_ENABLED=true)

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tedorigawa001-servicenow-mcp/close-incident.md

WHAT IT DOES

What close_incident does on ServiceNow-MCP

AI agents use close_incident to create or update resources in ServiceNow-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.

RISK

Why close_incident is rated Medium

This tool modifies incident records by changing their status to closed. While the change is reversible (incidents can be reopened), it represents a significant operational action that could impact incident tracking, SLA compliance, and audit trails. Categorized as Write rather than Destructive because closure is reversible.

From the tool's definition Tool name 'close_incident' and description 'Close a resolved incident (requires WRITE_ENABLED=true)' indicate modification of incident state. The WRITE_ENABLED flag confirms this is a write operation that changes data in ServiceNow.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs close_incident safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_incident, this is the rule to start with:

close_incident Rate-limited

close_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": {
    "close_incident": {
      "limits": [
        {
          "counter": "close_incident_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every close_incident call is checked against it from then on.

FAQ

Questions about close_incident

What does the close_incident tool do? +

Close a resolved incident (requires WRITE_ENABLED=true). It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_incident? +

Register the ServiceNow MCP server in PolicyLayer and add a rule for close_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. Nothing to install.

What risk level is close_incident? +

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

Can I rate-limit close_incident? +

Yes. Add a rate_limit block to the close_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 close_incident completely? +

Set action: deny in the PolicyLayer policy for close_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 close_incident? +

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

KEEP EXPLORING

More on ServiceNow, and thousands of servers like it.

This server

All 495 ServiceNow tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →