Delete a workflow from ServiceNow
AI agents call delete_workflow 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.
Deletion of workflows is an irreversible operation that destroys data and cannot be undone. Workflows in ServiceNow are often critical process automation components; deleting one could disrupt business processes, incident management, and service delivery. An AI agent misusing this tool could cause significant operational damage.
From the tool's definition Tool name 'delete_workflow' explicitly indicates deletion. Description states 'Delete a workflow from ServiceNow' confirming irreversible removal of data.
Attacks that exploit this kind of access
Delete a workflow from ServiceNow. 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_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 ServiceNow MCP Server. Nothing to install.
delete_workflow 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_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.
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.
delete_workflow is provided by the ServiceNow MCP Server MCP server (shameerampcome/servicenow-mcp). 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 →