drive_streamdiffusion

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/drive-streamdiffusion.md

WHAT IT DOES

What drive_streamdiffusion does on tdmcp — TouchDesigner MCP server

AI agents invoke drive_streamdiffusion 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 drive_streamdiffusion is rated High

This tool orchestrates a complex multi-step external operation: discovering and loading a .tox file, creating and wiring TouchDesigner components, configuring AI diffusion parameters, and optionally broadcasting output via streaming protocols. It triggers external operations (StreamDiffusion AI inference, Syphon/Spout/NDI output) whose effects depend on arguments.

From the tool's definition Wraps the community StreamDiffusionTD.tox into a one-shot Layer 1 setup: locate the .tox via candidate-path discovery, drop it into a fresh baseCOMP, wire a camera/source TOP into its input, set the prompt/strength/cfg/seed custom pars, and optionally…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs drive_streamdiffusion 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 drive_streamdiffusion, this is the rule to start with:

drive_streamdiffusion Rate-limited

drive_streamdiffusion 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": {
    "drive_streamdiffusion": {
      "limits": [
        {
          "counter": "drive_streamdiffusion_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 drive_streamdiffusion call is checked against it from then on.

FAQ

Questions about drive_streamdiffusion

What does the drive_streamdiffusion tool do? +

Wraps the community StreamDiffusionTD.tox (by dotsimulate) into a one-shot Layer 1 setup: locate the .tox via candidate-path discovery, drop it into a fresh baseCOMP, wire a camera/source TOP into its input, set the prompt/strength/cfg/seed custom pars, and optionally re-broadcast the output via Syphon/Spout or NDI. Returns a friendly error when the .tox is not installed. The result envelope includes validated_pars so downstream tools (create_ai_mirror) know which SD pars to bind a control panel to. 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 drive_streamdiffusion? +

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

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

Can I rate-limit drive_streamdiffusion? +

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

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

drive_streamdiffusion 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

All high-risk MCP tools → The MCP Attack Database →

Guides

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