delete_td_node
DESTRUCTIVE: permanently remove one node from the project by path (a COMP also takes its children with it); this cannot be undone via the API. Returns {deleted} with the path that was removed. Only call this when the user explicitly asks to delete a node.
This record as markdown: /tools/io-github-pantani-tdmcp/delete-td-node.md
What delete_td_node does on tdmcp — TouchDesigner MCP server
AI agents call delete_td_node to permanently remove resources in tdmcp — TouchDesigner MCP server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_td_node is rated Critical
This tool performs irreversible deletion of project data. It cannot be undone programmatically and removes both the target node and any child nodes. This meets the Destructive category definition precisely. Severity is high because deleting nodes in a visual project could cause significant loss of work, though it is scoped to a single node deletion (not a mass purge operation).
From the tool's definition Tool description explicitly labels it as 'DESTRUCTIVE: permanently remove one node from the project by path' and states 'this cannot be undone via the API.' The function irreversibly deletes nodes, and when a COMP is deleted, all its children are also removed.
Attacks that exploit this kind of access
The rule that runs delete_td_node safely
PolicyLayer is an MCP gateway: it sits between your AI agents and tdmcp — TouchDesigner MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_td_node, this is the rule to start with:
delete_td_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 tdmcp — TouchDesigner MCP server, apply this rule, and every delete_td_node call is checked against it from then on.
Questions about delete_td_node
DESTRUCTIVE: permanently remove one node from the project by path (a COMP also takes its children with it); this cannot be undone via the API. Returns {deleted} with the path that was removed. Only call this when the user explicitly asks to delete a node. It is categorised as a Destructive tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for delete_td_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 tdmcp — TouchDesigner MCP server. Nothing to install.
delete_td_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_td_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_td_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_td_node is provided by the tdmcp — TouchDesigner MCP server MCP server (@dpantani/tdmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.
Across the catalogue