resolume_vdmx_output_chain
Create an OSC control chain for driving Resolume, VDMX, or both from TouchDesigner. It builds target-specific OSC Out lanes with layer opacity, crossfader, speed, clip trigger, and blackout channels; use it beside video/NDI/Syphon output tools when an external VJ app handles playback or final com...
This record as markdown: /tools/io-github-pantani-tdmcp/resolume-vdmx-output-chain.md
What resolume_vdmx_output_chain does on tdmcp — TouchDesigner MCP server
AI agents invoke resolume_vdmx_output_chain 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.
Why resolume_vdmx_output_chain is rated High
This tool executes remote control commands via OSC protocol to external software systems (Resolume, VDMX), causing those applications to perform actions (layer opacity changes, clip triggers, blackout events, crossfader adjustments, speed control). The effects are observable in external systems and depend on the arguments (which channels, which values).
From the tool's definition The tool 'Create an OSC control chain for driving Resolume, VDMX, or both from TouchDesigner' explicitly triggers external operations ('driving' external VJ applications, 'builds target-specific OSC Out lanes' that control remote systems' layer opacity,…
Attacks that exploit this kind of access
The rule that runs resolume_vdmx_output_chain 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 resolume_vdmx_output_chain, this is the rule to start with:
resolume_vdmx_output_chain 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.
The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every resolume_vdmx_output_chain call is checked against it from then on.
Questions about resolume_vdmx_output_chain
Create an OSC control chain for driving Resolume, VDMX, or both from TouchDesigner. It builds target-specific OSC Out lanes with layer opacity, crossfader, speed, clip trigger, and blackout channels; use it beside video/NDI/Syphon output tools when an external VJ app handles playback or final compositing. 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.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for resolume_vdmx_output_chain: 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.
resolume_vdmx_output_chain is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the resolume_vdmx_output_chain 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.
Set action: deny in the PolicyLayer policy for resolume_vdmx_output_chain. 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.
resolume_vdmx_output_chain 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.
More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.
Across the catalogue