Permanently delete a workflow by ID. This cannot be undone. Two-phase flow (required): 1. Call with just workflowId to get a deletion preview. Response: { pendingDelete: true, id, name, status, relatedEntities: { executions, leads, timelines }, relatedEntitiesTruncated, confirmToken, expiresIn: 3...
Part of the Agentled server.
Free to start. No card required.
AI agents may call delete_workflow to permanently remove or destroy resources in Agentled. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call delete_workflow in a loop, permanently destroying resources in Agentled. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"delete_workflow"
]
}See the full Agentled policy for all 119 tools.
These attack patterns abuse exactly the kind of access delete_workflow gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Permanently delete a workflow by ID. This cannot be undone. Two-phase flow (required): 1. Call with just workflowId to get a deletion preview. Response: { pendingDelete: true, id, name, status, relatedEntities: { executions, leads, timelines }, relatedEntitiesTruncated, confirmToken, expiresIn: 300, expiresAt, message } Nothing is deleted in phase 1. Token is valid for 5 minutes. 2. Call again with both workflowId AND confirmToken to perform the cascade delete. Response: { deleted: true, id }. Server error responses (always structured JSON): - 404 { error: "Workflow not found" } — wrong ID or wrong workspace. - 403 { error: "Invalid or expired confirmation token. Request a new deletion preview first." } — token typo, expired, or workspace/workflow mismatch. - 500 { error: "Failed to delete workflow" } — cascade failure (rare; safe to retry phase 2 with a fresh token). If you see a bare "Denied." with no detail, that is your MCP host (Claude Desktop / Cursor / etc.) denying the destructive call at the approval-policy layer, not this server. Agentled never returns "Denied." — every error from this tool includes a JSON body. Check the host's tool-permission settings and re-approve, then retry.. It is categorised as a Destructive tool in the Agentled MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agentled 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 Agentled. 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 Agentled MCP server (@agentled/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 119 Agentled tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.