close_change_request
Close a change request with close code and notes (requires WRITE_ENABLED=true)
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/close-change-request.md
What close_change_request does on NowAIKit — ServiceNow AI Toolkit
AI agents use close_change_request to create or update resources in NowAIKit — ServiceNow AI Toolkit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NowAIKit — ServiceNow AI Toolkit environment.
Why close_change_request is rated Medium
This tool creates or modifies data reversibly by changing the status of a change request to 'closed' and recording associated metadata (close code and notes). While closing a change request has business consequences in IT change management workflows, the action itself is reversible (the request can be reopened). This places it in the Write category rather than Destructive.
From the tool's definition "Close a change request with close code and notes" — the tool modifies the state of a change request record by closing it, which is a reversible state change operation.
Attacks that exploit this kind of access
The rule that runs close_change_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and NowAIKit — ServiceNow AI Toolkit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_change_request, this is the rule to start with:
close_change_request 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 NowAIKit — ServiceNow AI Toolkit, apply this rule, and every close_change_request call is checked against it from then on.
Questions about close_change_request
Close a change request with close code and notes (requires WRITE_ENABLED=true). It is categorised as a Write tool in the NowAIKit — ServiceNow AI Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NowAIKit — ServiceNow AI Toolkit 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 NowAIKit — ServiceNow AI Toolkit. Nothing to install.
close_change_request 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 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.
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.
close_change_request is provided by the NowAIKit — ServiceNow AI Toolkit MCP server (nowaikit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on NowAIKit — ServiceNow AI Toolkit, and thousands of servers like it.
This server
Across the catalogue