Delete a chatflow or agentflow from Flowise.
AI agents call flowise_delete_flow to permanently remove resources in Flowise — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes chatflows or agentflows without reversal capability. Deletion of configured flows represents irreversible data loss that could disrupt AI agent operations or lose critical workflow definitions. While not financial or affecting external systems directly, the destructive nature warrants high severity due to the potential business impact of losing automation workflows.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a chatflow or agentflow from Flowise' — irreversible removal of workflow data.
Attacks that exploit this kind of access
Delete a chatflow or agentflow from Flowise. It is categorised as a Destructive tool in the Flowise MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Flowise MCP server in PolicyLayer and add a rule for flowise_delete_flow: 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 Flowise. Nothing to install.
flowise_delete_flow 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 flowise_delete_flow 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 flowise_delete_flow. 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.
flowise_delete_flow is provided by the Flowise MCP server (julidir/flowise-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 →