Permanently delete a ServiceNow record by sys_id. This action is irreversible. Args: - table (string): Table name - sys_id (string): sys_id of the record to delete Returns: Confirmation of deletion ⚠️ Destructive: This permanently removes the record. Use only when deletion is explicitly requested.
AI agents call servicenow_delete_record to permanently remove resources in Servicenow — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly deletes data from ServiceNow records by sys_id. This is a core destructive operation with no undo capability. Severity is 'high' rather than 'critical' because the blast radius is scoped to individual records (not bulk or cascading deletion like servicenow_bulk_delete), though the irreversibility warrants high severity.
From the tool's definition Tool description explicitly states 'Permanently delete a ServiceNow record' and 'This action is irreversible.' The warning section emphasizes 'This permanently removes the record.'
Attacks that exploit this kind of access
Permanently delete a ServiceNow record by sys_id. This action is irreversible. Args: - table (string): Table name - sys_id (string): sys_id of the record to delete Returns: Confirmation of deletion ⚠️ Destructive: This permanently removes the record. Use only when deletion is explicitly requested. It is categorised as a Destructive tool in the Servicenow 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 servicenow_delete_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. Nothing to install.
servicenow_delete_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 servicenow_delete_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 servicenow_delete_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.
servicenow_delete_record is provided by the Servicenow MCP server (kylburns89/servicenow-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →