rename_operator · Touchdesigner MCP: Risk & Policy

WHAT IT DOES

What rename_operator does on Touchdesigner

AI agents use rename_operator to create or update resources in Touchdesigner — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Touchdesigner environment.

WHY IT NEEDS A POLICY

Why rename_operator needs a policy

Renaming an operator in TouchDesigner modifies the operator's identity and any references to it, but is reversible—the operator can be renamed back. This is a Write operation (data modification) rather than Destructive (which would require deletion or irreversible loss).

From the tool's definition Tool description states 'Rename an operator', which modifies metadata of an existing operator. This is a reversible change to state (the operator still exists, only its name changes).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_operator Rate-limited

rename_operator stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_operator": {
      "limits": [
        {
          "counter": "rename_operator_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Touchdesigner, so you can run agents against it safely.

FAQ

Questions about rename_operator

What does the rename_operator tool do? +

Rename an operator. Returns its new full path. It is categorised as a Write tool in the Touchdesigner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_operator? +

Register the Touchdesigner MCP server in PolicyLayer and add a rule for rename_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.

What risk level is rename_operator? +

rename_operator is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_operator? +

Yes. Add a rate_limit block to the rename_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.

How do I block rename_operator completely? +

Set action: deny in the PolicyLayer policy for rename_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.

What MCP server provides rename_operator? +

rename_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.