delete_custom_node
Delete a custom node. This action cannot be undone.
This record as markdown: /tools/flowdot-llc-mcp-server/delete-custom-node.md
What delete_custom_node does on FlowDot MCP Server
AI agents call delete_custom_node 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_custom_node is rated Critical
The tool permanently removes a custom node from the FlowDot platform without recovery options. This meets the Destructive category definition as it irreversibly deletes data and cannot be undone. High severity reflects that misuse could result in loss of custom workflow components, though the blast radius is somewhat contained to individual node artifacts rather than system-wide impact.
From the tool's definition Tool name 'delete_custom_node' combined with description 'This action cannot be undone' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_custom_node 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_custom_node, this is the rule to start with:
delete_custom_node 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_custom_node call is checked against it from then on.
Questions about delete_custom_node
Delete a custom node. This action cannot be undone. 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_custom_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 FlowDot MCP Server. Nothing to install.
delete_custom_node 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_custom_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.
Set action: deny in the PolicyLayer policy for delete_custom_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.
delete_custom_node 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