删除指定的 Workflow
AI agents call delete_workflow to permanently remove resources in Argo Workflow MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a workflow is an irreversible operation that permanently removes data and cannot be undone. This matches the Destructive category definition. Severity is high because workflow deletion could disrupt operational processes and lose execution history, though the blast radius is scoped to a single workflow rather than cascading system-wide impacts (which would be critical).
From the tool's definition Tool name is 'delete_workflow' and description translates to 'Delete the specified Workflow'. The server description confirms deletion is a supported operation ('deletion'). No reversibility or undo capability is indicated.
Attacks that exploit this kind of access
删除指定的 Workflow. It is categorised as a Destructive tool in the Argo Workflow MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Argo Workflow 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 Argo Workflow 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 Argo Workflow MCP Server MCP server (yjx3097890/argo-workflow-mcp-server). 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 →