connect_qlab_cue_stack
Create a QLab OSC cue-stack scaffold with cue command maps, status, and rehearsal-focused setup notes.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-qlab-cue-stack.md
What connect_qlab_cue_stack does on tdmcp — TouchDesigner MCP server
AI agents use connect_qlab_cue_stack to create or update resources in tdmcp — TouchDesigner MCP server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your tdmcp — TouchDesigner MCP server environment.
Why connect_qlab_cue_stack is rated Medium
This tool creates new QLab (a theater cueing system) configuration scaffolds including OSC mappings and setup documentation. While it modifies state by establishing new cue structures, these are reversible and intended for rehearsal/setup purposes rather than destructive operations. The blast radius is medium—misconfigured cue stacks could disrupt theater productions, but the changes are restorable.
From the tool's definition Tool description states it will 'Create a QLab OSC cue-stack scaffold', indicating creation of new data/configuration structures. The term 'Create' and 'scaffold' suggests reversible generation of OSC command mappings and setup notes.
Attacks that exploit this kind of access
The rule that runs connect_qlab_cue_stack 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 connect_qlab_cue_stack, this is the rule to start with:
connect_qlab_cue_stack stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 connect_qlab_cue_stack call is checked against it from then on.
Questions about connect_qlab_cue_stack
Create a QLab OSC cue-stack scaffold with cue command maps, status, and rehearsal-focused setup notes. It is categorised as a Write tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for connect_qlab_cue_stack: 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.
connect_qlab_cue_stack is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the connect_qlab_cue_stack 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 connect_qlab_cue_stack. 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.
connect_qlab_cue_stack 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.
This server
Across the catalogue