Destroy the operator at path.
AI agents call delete_operator to permanently remove resources in Touchdesigner — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes operators from a TouchDesigner project. The deletion cannot be undone programmatically (undo would require user action or external state management). While the blast radius is constrained to the TouchDesigner instance rather than system-wide data, the irreversible nature of destruction and potential loss of project work justifies 'Destructive' classification.
From the tool's definition Tool name: 'delete_operator'; Description: 'Destroy the operator at `path`.' The verb 'Destroy' combined with the action of removing an operator indicates an irreversible deletion operation.
Attacks that exploit this kind of access
Destroy the operator at path. It is categorised as a Destructive tool in the Touchdesigner MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Touchdesigner MCP server in PolicyLayer and add a rule for delete_operator: 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 Touchdesigner. Nothing to install.
delete_operator 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_operator 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_operator. 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_operator is provided by the Touchdesigner MCP server (mrinalghosh/touchdesigner-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 →