create_depth_pop_field

Build a depth-driven GPU POP scatter field: consumes a depth/mask TOP and uses

SERVERtdmcp — TouchDesigner MCP server SOURCE@dpantani/tdmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pantani-tdmcp/create-depth-pop-field.md

WHAT IT DOES

What create_depth_pop_field does on tdmcp — TouchDesigner MCP server

AI agents invoke create_depth_pop_field to trigger actions in tdmcp — TouchDesigner MCP server. 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.

RISK

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_depth_pop_field safely

PolicyLayer is an MCP gateway: it sits between your AI agents and tdmcp — TouchDesigner MCP server, 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:

create_depth_pop_field Rate-limited

create_depth_pop_field stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every create_depth_pop_field call is checked against it from then on.

FAQ

Questions about create_depth_pop_field

What does the create_depth_pop_field tool do? +

Build a depth-driven GPU POP scatter field: consumes a depth/mask TOP and uses. It is categorised as a Execute tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_depth_pop_field? +

Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for create_depth_pop_field: 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 create_depth_pop_field? +

create_depth_pop_field is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_depth_pop_field? +

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

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

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

KEEP EXPLORING

More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.

This server

All 334 tdmcp — TouchDesigner MCP server tools → High-risk tools on this server →

Across the catalogue

diagram_create on Templonix Lite MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →