delete_workflow

THE RISK

Critical Risk

Why delete_workflow needs a policy

Deleting a workflow definition is an irreversible action that removes automation logic from the ServiceNow system. This cannot be undone without restoration from backups. While the blast radius is limited to the specific workflow (not system-wide data deletion), the destructive nature and potential operational impact on dependent processes justifies the 'Destructive' category over 'Execute'.

From the tool's definition Tool name: 'delete_workflow'; description: 'Delete a workflow definition from ServiceNow.' The use of 'Delete' as the primary verb indicates irreversible removal of a workflow definition.

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

POLICY

How to control delete_workflow

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_workflow"
  ]
}

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

Create a free account and register Snow — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Snow tools

Destructive delete_script_include Delete a Script Include from ServiceNow. Destructive delete_story_dependency Deletes an existing dependency relationship between user stories. Destructive remove_group_members Remove multiple users from a group. Execute publish_changeset Publish a completed changeset so it can be retrieved from the remote instance. Write add_change_task Adds a new task to an existing change request. Write add_comment_to_incident Adds a customer-visible comment (updates the 'comments' field) to an existing incident. Write add_comment_to_request Adds a customer-visible comment to a request ticket (REQ). Write add_file_to_changeset Add (track) a configuration record inside the specified changeset.

All 88 Snow tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Snow → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_workflow

What does the delete_workflow tool do? +

Delete a workflow definition from ServiceNow. It is categorised as a Destructive tool in the Snow 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 delete_workflow? +

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

What risk level is delete_workflow? +

delete_workflow 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 delete_workflow? +

Yes. Add a rate_limit block to the delete_workflow 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 delete_workflow completely? +

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

delete_workflow is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Snow tool call.

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

CHECK YOUR STACK →