Delete a specific workflow.
AI agents call delete_workflow to permanently remove resources in Unstructured API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a workflow configuration from the Unstructured API, which cannot be undone. Deletion is irreversible and represents a destructive action. While the blast radius is somewhat limited to the workflow itself (not cascading financial or system-wide damage in most cases), the inability to recover the deleted workflow justifies the 'Destructive' category and 'high' severity.
From the tool's definition Tool name is 'delete_workflow' with description 'Delete a specific workflow.' The verb 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a specific workflow. It is categorised as a Destructive tool in the Unstructured API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Unstructured API 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 Unstructured API 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 Unstructured API MCP Server MCP server (liuchongchong1995/uns-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 →