connect_lighting_console_osc
Create a safety-gated OSC command scaffold for grandMA3, ETC Eos, ChamSys, Avolites, or generic lighting consoles without sending direct DMX.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-lighting-console-osc.md
What connect_lighting_console_osc does on tdmcp — TouchDesigner MCP server
AI agents use connect_lighting_console_osc 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_lighting_console_osc is rated Medium
The tool creates an OSC command scaffold (a Write action), but does not execute or transmit commands to hardware. The safety gate and no-direct-DMX clause prevent it from being Execute. Severity is medium because misconfigured OSC scaffolding could inadvertently trigger lighting changes when later activated, but the tool itself only writes configuration.
From the tool's definition 'Create a safety-gated OSC command scaffold' and 'without sending direct DMX' — the tool creates/writes a scaffold structure for OSC commands but explicitly does not send live DMX signals
Attacks that exploit this kind of access
The rule that runs connect_lighting_console_osc 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_lighting_console_osc, this is the rule to start with:
connect_lighting_console_osc 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_lighting_console_osc call is checked against it from then on.
Questions about connect_lighting_console_osc
Create a safety-gated OSC command scaffold for grandMA3, ETC Eos, ChamSys, Avolites, or generic lighting consoles without sending direct DMX. 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_lighting_console_osc: 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_lighting_console_osc 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_lighting_console_osc 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_lighting_console_osc. 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_lighting_console_osc 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