create_safety_blackout_chain
Build a live-show safety primitive at the very end of the master output chain: deterministic fade-to-black over a configurable time, optional emergency single-frame hard-cut, optional hotkey + external watchdog trigger, and symmetric fade-in recovery. All reactivity is parameter-driven (Speed + L...
This record as markdown: /tools/hybridlabor-api-aos/create-safety-blackout-chain.md
What create_safety_blackout_chain does on Aos
AI agents use create_safety_blackout_chain 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_safety_blackout_chain is rated Medium
This tool creates a new node chain (container, composite, output nodes, etc.) in the TouchDesigner project. It is a Write operation — it builds and configures network nodes reversibly. While it involves 'emergency' and 'blackout' language, these are UI/visual safety controls, not destructive data deletion. No code execution at cook time is explicitly noted ('no Python runs at cook time').
From the tool's definition 'Build a live-show safety primitive', 'Returns the container, source, dim, emergency-gate, composite, and output node' — creates and wires nodes in the TouchDesigner network
Attacks that exploit this kind of access
The rule that runs create_safety_blackout_chain 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_safety_blackout_chain, this is the rule to start with:
create_safety_blackout_chain 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_safety_blackout_chain call is checked against it from then on.
Questions about create_safety_blackout_chain
Build a live-show safety primitive at the very end of the master output chain: deterministic fade-to-black over a configurable time, optional emergency single-frame hard-cut, optional hotkey + external watchdog trigger, and symmetric fade-in recovery. All reactivity is parameter-driven (Speed + Lookup CHOP + Math/Logic CHOPs) — no Python runs at cook time, so the chain is ALLOW_EXEC=0-safe. Complements create_panic (per-source kill+freeze) by being the master-output dimmer with grace, recovery, and a watchdog hook. Returns the container, source, dim, emergency-gate, composite, and output node paths plus the trigger merge/target/speed/lookup nodes. 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_safety_blackout_chain: 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_safety_blackout_chain 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_safety_blackout_chain 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_safety_blackout_chain. 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_safety_blackout_chain 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