move_operator · Touchdesigner MCP: Risk & Policy

WHAT IT DOES

What move_operator does on Touchdesigner

AI agents use move_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 move_operator needs a policy

Moving an operator's tile changes its position in the UI layout. This is a reversible visual/spatial modification (it can be moved back), with no data deletion or code execution. It writes/updates the operator's position metadata, hence Write category with low severity since it only affects visual arrangement.

From the tool's definition Move an operator's tile in the network editor

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_operator Rate-limited

move_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": {
    "move_operator": {
      "limits": [
        {
          "counter": "move_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 move_operator

What does the move_operator tool do? +

Move an operator's tile in the network editor. 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 move_operator? +

Register the Touchdesigner MCP server in PolicyLayer and add a rule for move_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 move_operator? +

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

Can I rate-limit move_operator? +

Yes. Add a rate_limit block to the move_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 move_operator completely? +

Set action: deny in the PolicyLayer policy for move_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 move_operator? +

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