Delete node and its edges
AI agents call delete_node to permanently remove resources in Pulse Workflow MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (nodes and their edges) from a workflow. While the impact is scoped to the specific workflow being edited (not system-wide), deletion operations are categorized as Destructive. Severity is high rather than critical because the blast radius is limited to a single workflow artifact, though loss of workflow structure and logic is significant.
From the tool's definition Tool name is 'delete_node' and description states 'Delete node and its edges' — uses the word 'Delete' which is irreversible. Deleting a node and its connections from a workflow cannot be undone without reconstruction.
Attacks that exploit this kind of access
Delete node and its edges. It is categorised as a Destructive tool in the Pulse Workflow MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pulse Workflow MCP Server MCP server in PolicyLayer and add a rule for delete_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 Pulse Workflow MCP Server. Nothing to install.
delete_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_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_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_node is provided by the Pulse Workflow MCP Server MCP server (pulse-intelligence/pulse-workflow-mcp). 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 →