create_dmx_fixture_pipeline
Build a DMX/Art-Net (or sACN) output chain from a fixture list. For each fixture (rgb, rgbw, par64, movingHead8, movingHead16) creates a Constant CHOP with one named, default-valued channel per DMX slot (prefixed
This record as markdown: /tools/hybridlabor-api-aos/create-dmx-fixture-pipeline.md
What create_dmx_fixture_pipeline does on Aos
AI agents use create_dmx_fixture_pipeline to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
Why create_dmx_fixture_pipeline is rated Medium
This tool creates new nodes and configures a DMX output pipeline in TouchDesigner. It is a creative/constructive operation that builds new data structures (Constant CHOPs, channels) without irreversibly destroying existing data. It may trigger external DMX/Art-Net output to physical lighting fixtures, but the primary action is creating and configuring nodes, placing it in Write.
From the tool's definition 'Build a DMX/Art-Net (or sACN) output chain from a fixture list... creates a Constant CHOP with one named, default-valued channel per DMX slot'
Attacks that exploit this kind of access
The rule that runs create_dmx_fixture_pipeline safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_dmx_fixture_pipeline, this is the rule to start with:
create_dmx_fixture_pipeline 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 Aos, apply this rule, and every create_dmx_fixture_pipeline call is checked against it from then on.
Questions about create_dmx_fixture_pipeline
Build a DMX/Art-Net (or sACN) output chain from a fixture list. For each fixture (rgb, rgbw, par64, movingHead8, movingHead16) creates a Constant CHOP with one named, default-valued channel per DMX slot (prefixed. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aos MCP server in PolicyLayer and add a rule for create_dmx_fixture_pipeline: 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 Aos. Nothing to install.
create_dmx_fixture_pipeline 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 create_dmx_fixture_pipeline 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_dmx_fixture_pipeline. 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_dmx_fixture_pipeline is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue