Delete multiple records matching a query. Dry-run by default — always preview before committing. Args: - table (string): Target table - query (string): Encoded query to select records to delete - dry_run (boolean): Preview without deleting (default: true). Set false to commit. - limit (number): S...
AI agents call servicenow_bulk_delete 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.
This tool irreversibly deletes data at scale. Even with dry_run as default, the ability to set dry_run=false with a limit up to 100 records creates high blast radius for accidental or malicious bulk deletion of business-critical ServiceNow records (incidents, changes, configurations). Permanent data loss is the defining characteristic of Destructive category, which outranks Execute and Write.
From the tool's definition Tool name is 'servicenow_bulk_delete' and description states 'Delete multiple records matching a query' and 'Deletion is permanent.' The dry_run parameter defaults to true but can be set to false to 'commit' the deletion.
Attacks that exploit this kind of access
Delete multiple records matching a query. Dry-run by default — always preview before committing. Args: - table (string): Target table - query (string): Encoded query to select records to delete - dry_run (boolean): Preview without deleting (default: true). Set false to commit. - limit (number): Safety cap — max records to delete (default 20, max 100) - response_format: Output format ⚠️ Deletion is permanent. Always run with dry_run=true first to confirm scope. Examples: - Preview stale test incidents → table=. 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_bulk_delete: 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_bulk_delete 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_bulk_delete 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_bulk_delete. 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_bulk_delete 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 →