delete_flow
Delete a flow and all its nodes and edges. Referenced bots are not deleted.
This record as markdown: /tools/instantkom-mcp-server/delete-flow.md
What delete_flow does on instantKOM MCP Server
AI agents call delete_flow to permanently remove resources in instantKOM MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_flow is rated Critical
This tool permanently deletes flows and associated nodes/edges, which cannot be undone. Even though referenced bots are preserved, the flow itself and its complete structure are irreversibly destroyed. This is a destructive operation with a potentially significant blast radius if triggered accidentally on critical automation flows in a messenger platform.
From the tool's definition 'Delete a flow and all its nodes and edges' — the tool irreversibly removes entire flow structures from the instantKOM platform. The verb 'Delete' combined with 'all its nodes and edges' indicates permanent data destruction without recovery mechanism.
Attacks that exploit this kind of access
The rule that runs delete_flow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_flow, this is the rule to start with:
delete_flow is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every delete_flow call is checked against it from then on.
Questions about delete_flow
Delete a flow and all its nodes and edges. Referenced bots are not deleted. It is categorised as a Destructive tool in the instantKOM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for 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 instantKOM MCP Server. Nothing to install.
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 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 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.
delete_flow is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
Across the catalogue