Critical Risk →

query_delete_records

Find records matching an encoded query and delete them all.

How to control query_delete_records ↓

What query_delete_records does on Now Sdk Ext

AI agents call query_delete_records to permanently remove resources in Now Sdk Ext — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why query_delete_records needs a policy

This tool performs bulk deletion of all records matching a query. This is irreversible and could wipe large amounts of data from a ServiceNow instance if misused. The blast radius is critical since a broad query could delete thousands of records across any table.

From the tool's definition 'Find records matching an encoded query and delete them all' — bulk deletion of records matching a query, which is irreversible.

Documented attack patterns abuse exactly the kind of access query_delete_records gives an agent:

How to control query_delete_records

PolicyLayer is an MCP gateway — it sits between your AI agents and Now Sdk Ext, and nothing reaches the server without passing your rules. This is the rule we recommend for query_delete_records:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "query_delete_records"
  ]
}

query_delete_records disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Now Sdk Ext — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about query_delete_records

What does the query_delete_records tool do? +

Find records matching an encoded query and delete them all. It is categorised as a Destructive tool in the Now Sdk Ext MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on query_delete_records? +

Register the Now Sdk Ext MCP server in PolicyLayer and add a rule for query_delete_records: 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 Now Sdk Ext. Nothing to install.

What risk level is query_delete_records? +

query_delete_records is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit query_delete_records? +

Yes. Add a rate_limit block to the query_delete_records 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.

How do I block query_delete_records completely? +

Set action: deny in the PolicyLayer policy for query_delete_records. 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.

What MCP server provides query_delete_records? +

query_delete_records is provided by the Now Sdk Ext MCP server (sonisoft-cnanda/now-sdk-ext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Now Sdk Ext tool call.

Start from Now Sdk Ext, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

86 Now Sdk Ext tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.