close_incident

Close a resolved incident (requires WRITE_ENABLED=true)

SERVERServiceNow MCP Server SOURCE@aartiq/servicenow-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity verified Pull the record →

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

What close_incident does on ServiceNow MCP Server

AI agents use close_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 close_incident is rated Medium

This tool creates a state change in ServiceNow's incident management system by closing an incident record. While the action itself is reversible (incidents can be reopened), it represents a significant modification to operational data that affects incident lifecycle and tracking. Closing incidents can impact SLA tracking, reporting, and team workflows.

From the tool's definition Tool name 'close_incident' and description 'Close a resolved incident' explicitly modifies incident state. The requirement flag 'WRITE_ENABLED=true' confirms this is a write operation that changes data in ServiceNow.

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 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 close_incident? +

Register the ServiceNow MCP Server 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 Server. 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 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ServiceNow MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.