rollback_changes
Delete a set of previously-created records, e.g. the rollback_token returned by bulk_create_records. Requires WRITE_ENABLED=true.
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/rollback-changes.md
What rollback_changes does on NowAIKit — ServiceNow AI Toolkit
AI agents call rollback_changes to permanently remove resources in NowAIKit — ServiceNow AI Toolkit, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why rollback_changes is rated Critical
This tool permanently deletes records without recovery options, matching the Destructive category definition. While framed as a 'rollback' operation, the core function is deletion. The severity is high because it can irreversibly remove multiple records at scale (bulk context), though blast radius depends on how an agent selects the rollback_token.
From the tool's definition 'Delete a set of previously-created records' and 'rollback_token returned by bulk_create_records' indicate irreversible deletion of data. The requirement for WRITE_ENABLED=true suggests admin-level impact.
Attacks that exploit this kind of access
The rule that runs rollback_changes 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 rollback_changes, this is the rule to start with:
rollback_changes is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect NowAIKit — ServiceNow AI Toolkit, apply this rule, and every rollback_changes call is checked against it from then on.
Questions about rollback_changes
Delete a set of previously-created records, e.g. the rollback_token returned by bulk_create_records. Requires WRITE_ENABLED=true. It is categorised as a Destructive tool in the NowAIKit — ServiceNow AI Toolkit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the NowAIKit — ServiceNow AI Toolkit MCP server in PolicyLayer and add a rule for rollback_changes: 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.
rollback_changes is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rollback_changes 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 rollback_changes. 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.
rollback_changes 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.
Across the catalogue