Delete a WorkFlowy node and all its children
AI agents call workflowy_delete_node to permanently remove resources in WorkFlowy MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data without the ability to undo the operation. Deletion of a node cascades to all children, creating a broad blast radius. An AI agent given this tool could accidentally or maliciously destroy significant portions of a user's outline and task hierarchy.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a WorkFlowy node and all its children' — this is an irreversible removal of data including all descendants.
Documented attack patterns abuse exactly the kind of access workflowy_delete_node gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WorkFlowy MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for workflowy_delete_node:
{
"version": "1",
"default": "deny",
"hide": [
"workflowy_delete_node"
]
} workflowy_delete_node disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a WorkFlowy node and all its children. It is categorised as a Destructive tool in the WorkFlowy MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WorkFlowy MCP Server MCP server in PolicyLayer and add a rule for workflowy_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 WorkFlowy MCP Server. Nothing to install.
workflowy_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 workflowy_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 workflowy_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.
workflowy_delete_node is provided by the WorkFlowy MCP Server MCP server (vladzima/workflowy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WorkFlowy MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 WorkFlowy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.