delete-flow
AI agents call delete-flow to permanently remove resources in Node Red — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes flow configurations from Node-RED. While the description is empty, the tool name unambiguously indicates destructive action (delete). Given that flows represent critical automation logic and deletion is irreversible, this poses a high blast radius if misused by an AI agent—it could disable automations, interrupt services, or erase important workflow definitions.
From the tool's definition Tool name 'delete-flow' combined with context of Node-RED flow management. The verb 'delete' indicates irreversible removal. Node-RED flows are workflow configurations; deletion removes automation logic that cannot be recovered without backup.
Attacks that exploit this kind of access
delete-flow. It is categorised as a Destructive tool in the Node Red MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Node Red MCP server in PolicyLayer and add a rule for delete-flow: 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 Node Red. Nothing to install.
delete-flow 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-flow 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-flow. 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-flow is provided by the Node Red MCP server (node-red-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →