create_phrase_locked_cue_engine
Build a DJ/VJ phrase-quantized cue-lock engine. Any incoming pulse CHOP (Button, MIDI In, OSC In, composeCueList trigger) is queued FIFO and fired on the next 1/2/4/8/16/32/64-bar phrase boundary derived from the global project tempo. Live controls: Active (on/off gate), PhraseLength (live retune...
This record as markdown: /tools/io-github-pantani-tdmcp/create-phrase-locked-cue-engine.md
What create_phrase_locked_cue_engine does on tdmcp — TouchDesigner MCP server
AI agents invoke create_phrase_locked_cue_engine 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 create_phrase_locked_cue_engine is rated High
This tool constructs and activates a real-time cue engine in TouchDesigner that triggers external operations (cue pulses from MIDI, OSC, CHOP signals) on tempo-synchronized boundaries. It doesn't just write static data — it creates an active execution system that fires events and controls live AV output. The 'Flush' control and FIFO queue management indicate ongoing execution behavior with dynamic side effects.
From the tool's definition Build a DJ/VJ phrase-quantized cue-lock engine... fired on the next 1/2/4/8/16/32/64-bar phrase boundary... Live controls: Active (on/off gate), PhraseLength (live retune), Flush (clear queue)
Attacks that exploit this kind of access
The rule that runs create_phrase_locked_cue_engine 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_phrase_locked_cue_engine, this is the rule to start with:
create_phrase_locked_cue_engine 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 create_phrase_locked_cue_engine call is checked against it from then on.
Questions about create_phrase_locked_cue_engine
Build a DJ/VJ phrase-quantized cue-lock engine. Any incoming pulse CHOP (Button, MIDI In, OSC In, composeCueList trigger) is queued FIFO and fired on the next 1/2/4/8/16/32/64-bar phrase boundary derived from the global project tempo. Live controls: Active (on/off gate), PhraseLength (live retune), Flush (clear queue), QueueDepth (display). Mode. 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 create_phrase_locked_cue_engine: 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.
create_phrase_locked_cue_engine 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 create_phrase_locked_cue_engine 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 create_phrase_locked_cue_engine. 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.
create_phrase_locked_cue_engine 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