delete_record
A destructive tool on the ServiceNow MCP server.
This record as markdown: /tools/io-github-jschuller-mcp-server-servicenow/delete-record.md
What delete_record does on ServiceNow MCP Server
AI agents call delete_record to permanently remove resources in ServiceNow MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_record is rated Critical
Despite empty description, the name 'delete_record' is unambiguous: it deletes data. In ServiceNow's context (CMDB, update sets, configuration management), deleting records destroys business-critical information irreversibly. This matches the Destructive category definition.
From the tool's definition Tool name 'delete_record' indicates irreversible deletion of data. ServiceNow is an enterprise CMDB/change management system where records represent critical business assets, configurations, and audit trails. Deletion cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete_record safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_record, this is the rule to start with:
delete_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 Server, apply this rule, and every delete_record call is checked against it from then on.
Questions about delete_record
delete_record is a destructive tool on the ServiceNow MCP Server MCP server. It is categorised as a Destructive tool in the ServiceNow MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for 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 MCP Server. Nothing to install.
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 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 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.
delete_record is provided by the ServiceNow MCP Server MCP server (pypi:mcp-server-servicenow). 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