create_cue_sequencer
Build a bar-quantized cue timeline: a Beat CHOP (on the global tempo) + a CHOP Execute DAT that, on each bar (or beat) boundary, advances through an ordered list of steps and recalls — or morphs over morph_seconds — that step
This record as markdown: /tools/io-github-pantani-tdmcp/create-cue-sequencer.md
What create_cue_sequencer does on tdmcp — TouchDesigner MCP server
AI agents invoke create_cue_sequencer 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_cue_sequencer is rated High
This tool creates and wires together live execution components in TouchDesigner (a Beat CHOP and a CHOP Execute DAT) that actively run logic on every bar/beat boundary, triggering state changes and morphs. It constructs executable, running operators in the project — this is an Execute-class operation because it sets up ongoing automated execution of code/logic, not merely writing static data.
From the tool's definition 'Build a bar-quantized cue timeline: a Beat CHOP (on the global tempo) + a CHOP Execute DAT that, on each bar (or beat) boundary, advances through an ordered list of steps and recalls — or morphs over morph_seconds — that step'
Attacks that exploit this kind of access
The rule that runs create_cue_sequencer 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_cue_sequencer, this is the rule to start with:
create_cue_sequencer 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_cue_sequencer call is checked against it from then on.
Questions about create_cue_sequencer
Build a bar-quantized cue timeline: a Beat CHOP (on the global tempo) + a CHOP Execute DAT that, on each bar (or beat) boundary, advances through an ordered list of steps and recalls — or morphs over morph_seconds — that step. 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_cue_sequencer: 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_cue_sequencer 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_cue_sequencer 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_cue_sequencer. 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_cue_sequencer 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