New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_td_node

Safely remove or bypass one TouchDesigner node. mode:

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/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 permanently removes nodes from a TouchDesigner visual system, which cannot be undone without undo functionality external to the tool itself. Deletion of nodes constitutes destructive action as it irreversibly alters the project structure. While described as 'safe,' the core operation is removal of data/components.

From the tool's definition Tool name explicitly states 'delete_td_node' and description says 'Safely remove or bypass one TouchDesigner node.' The verb 'delete' combined with 'remove' indicates irreversible deletion of a node from a TouchDesigner project.

Questions about delete_td_node

What does the delete_td_node tool do? +

Safely remove or bypass one TouchDesigner node. mode:. 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.

How do I enforce a policy on delete_td_node? +

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.

What risk level is delete_td_node? +

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.

Can I rate-limit delete_td_node? +

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.

How do I block delete_td_node completely? +

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.

What MCP server provides delete_td_node? +

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.

// 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 tdmcp — TouchDesigner 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.