delete_connection
Remove a connection between two nodes in a workflow.
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.
Attacks that exploit this kind of access
The rule that runs delete_connection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_connection, this is the rule to start with:
delete_connection 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 FlowDot MCP Server, apply this rule, and every delete_connection call is checked against it from then on.
Questions about delete_connection
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.
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.
delete_connection 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_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.
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.
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.
Across the catalogue