restore_archived_record
Schedule a one-time standard ServiceNow restore for one archive log entry. The archive row is removed after successful restore. [Destructive]
This record as markdown: /tools/tedorigawa001-servicenow-mcp/restore-archived-record.md
What restore_archived_record does on ServiceNow-MCP
AI agents call restore_archived_record to permanently remove resources in ServiceNow-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why restore_archived_record is rated Critical
Restoring removes the archive row irreversibly, marked explicitly as destructive.
From the tool's definition archive row is removed after successful restore [Destructive]
Attacks that exploit this kind of access
The rule that runs restore_archived_record 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 restore_archived_record, this is the rule to start with:
restore_archived_record 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 ServiceNow-MCP, apply this rule, and every restore_archived_record call is checked against it from then on.
Questions about restore_archived_record
Schedule a one-time standard ServiceNow restore for one archive log entry. The archive row is removed after successful restore. [Destructive]. It is categorised as a Destructive tool in the ServiceNow-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceNow MCP server in PolicyLayer and add a rule for restore_archived_record: 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.
restore_archived_record 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 restore_archived_record 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 restore_archived_record. 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.
restore_archived_record 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.
More on ServiceNow, and thousands of servers like it.
Across the catalogue