close_change_request

Close a change request with close code and notes (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-change-request.md

What close_change_request does on ServiceNow MCP Server

AI agents use close_change_request 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_change_request is rated Medium

Closing a change request is a reversible modification operation that changes the status and properties of an existing record. While significant (it finalizes workflow state), it is not destructive because the record persists and can theoretically be reopened or the change tracked. This qualifies as Write rather than Destructive.

From the tool's definition Tool description explicitly states 'Close a change request' with 'close code and notes', which modifies the state of a change request record. Requires 'WRITE_ENABLED=true', indicating it performs a write operation.

Questions about close_change_request

What does the close_change_request tool do? +

Close a change request with close code and notes (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_change_request? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for close_change_request: 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_change_request? +

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

Can I rate-limit close_change_request? +

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

Set action: deny in the PolicyLayer policy for close_change_request. 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_change_request? +

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