create_depth_pop_field

What create_depth_pop_field does on Aos

AI agents invoke create_depth_pop_field to trigger actions in Aos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why create_depth_pop_field is rated High

The tool constructs and runs a GPU POP (Particle Operator) scatter field, which involves executing GPU computations and creating interconnected nodes in a live visual system. This goes beyond merely writing data — it triggers active GPU execution pipelines. The blast radius is high because misuse could create runaway GPU particle systems that consume significant system resources in a live TouchDesigner environment.

From the tool's definition 'Build a depth-driven GPU POP scatter field: consumes a depth/mask TOP and uses' — this tool triggers GPU-based particle system execution within TouchDesigner, consuming inputs and generating live visual processing nodes

The rule that runs create_depth_pop_field safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_depth_pop_field, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_depth_pop_field": {
      "limits": [
        {
          "counter": "create_depth_pop_field_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about create_depth_pop_field