delete_custom_node

Delete a custom node. This action cannot be undone.

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

Questions about delete_custom_node

What does the delete_custom_node tool do? +

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.

How do I enforce a policy on delete_custom_node? +

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.

What risk level is delete_custom_node? +

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.

Can I rate-limit delete_custom_node? +

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.

How do I block delete_custom_node completely? +

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.

What MCP server provides delete_custom_node? +

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.

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