create_chroma_reactive
[experimental] Builds a 12-channel pitch-class chroma vector (chroma_0..chroma_11) from an audio bus via FFT bin → pitch-class fold. Outputs a Null CHOP ready for bind_to_channel. Shares audioSource convention with create_transient_reactive / create_energy_reactive.
This record as markdown: /tools/hybridlabor-api-aos/create-chroma-reactive.md
What create_chroma_reactive does on Aos
AI agents use create_chroma_reactive 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_chroma_reactive is rated Medium
This tool creates new nodes/operators in the TouchDesigner network (a Null CHOP output), which is a reversible write/create operation. It does not delete data, execute arbitrary code, or involve financial transactions. Misuse could clutter or disrupt a project network but is recoverable.
From the tool's definition Builds a 12-channel pitch-class chroma vector from an audio bus via FFT bin → pitch-class fold. Outputs a Null CHOP ready for bind_to_channel.
Attacks that exploit this kind of access
The rule that runs create_chroma_reactive 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_chroma_reactive, this is the rule to start with:
create_chroma_reactive 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_chroma_reactive call is checked against it from then on.
Questions about create_chroma_reactive
[experimental] Builds a 12-channel pitch-class chroma vector (chroma_0..chroma_11) from an audio bus via FFT bin → pitch-class fold. Outputs a Null CHOP ready for bind_to_channel. Shares audioSource convention with create_transient_reactive / create_energy_reactive. 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_chroma_reactive: 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_chroma_reactive 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_chroma_reactive 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_chroma_reactive. 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_chroma_reactive 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