delete_flow_node

Remove a node from a flow. Also removes connected edges. The bot is not deleted.

SERVERinstantKOM MCP Server SOURCEinstantkom/mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/instantkom-mcp-server/delete-flow-node.md

What delete_flow_node does on instantKOM MCP Server

AI agents call delete_flow_node 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_node is rated Critical

This tool permanently deletes flow nodes and their connected edges, which cannot be automatically undone. While the bot itself is preserved, the flow architecture is modified irreversibly. The high severity reflects that deleting flow nodes could disrupt automation workflows and messaging operations on the instantKOM platform, potentially affecting live chat/messenger functionality.

From the tool's definition delete_flow_node description explicitly states 'Remove a node from a flow. Also removes connected edges.' The verb 'Remove' combined with the irreversible deletion of flow structure elements (nodes and edges) indicates destructive action.

Questions about delete_flow_node

What does the delete_flow_node tool do? +

Remove a node from a flow. Also removes connected edges. The bot is 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.

How do I enforce a policy on delete_flow_node? +

Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for delete_flow_node: 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.

What risk level is delete_flow_node? +

delete_flow_node is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_flow_node? +

Yes. Add a rate_limit block to the delete_flow_node 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.

How do I block delete_flow_node completely? +

Set action: deny in the PolicyLayer policy for delete_flow_node. 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.

What MCP server provides delete_flow_node? +

delete_flow_node 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of instantKOM MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.