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 performs an irreversible deletion operation on a workflow resource. Once deleted, the workflow and potentially associated configurations cannot be recovered without manual intervention or backups. The destructive nature (irreversible data removal) takes precedence over Write category.
From the tool's definition Tool name is 'delete_workflow' and description states 'Delete a specific workflow.' The verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_workflow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unstructured API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_workflow:
{
"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.
Free to start. No card required.
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 (unstructured-io/uns-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Unstructured API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 Unstructured API MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.