delete_connection

Remove a connection between two nodes in a workflow.

SERVERFlowDot MCP Server SOURCEflowdot-llc/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/flowdot-llc-mcp-server/delete-connection.md

What delete_connection does on FlowDot MCP Server

AI agents call delete_connection to permanently remove resources in FlowDot MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_connection is rated Critical

Deleting connections in a workflow modifies the structure irreversibly and cannot be automatically undone. While not data deletion per se, it destroys workflow configuration that users have created. This is destructive rather than merely Write because connections, once removed, require manual reconstruction and the action cannot be rolled back without external version control.

From the tool's definition Tool named 'delete_connection' with description 'Remove a connection between two nodes in a workflow.' The verb 'Remove' combined with 'delete' in the function name indicates irreversible deletion of workflow state.

Questions about delete_connection

What does the delete_connection tool do? +

Remove a connection between two nodes in a workflow. It is categorised as a Destructive tool in the FlowDot 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_connection? +

Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for delete_connection: 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 FlowDot MCP Server. Nothing to install.

What risk level is delete_connection? +

delete_connection 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_connection? +

Yes. Add a rate_limit block to the delete_connection 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_connection completely? +

Set action: deny in the PolicyLayer policy for delete_connection. 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_connection? +

delete_connection is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on FlowDot 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 FlowDot 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.