bind_audio_reactive
Make a whole COMP react to the music in one call — the core VJ move. Point
This record as markdown: /tools/hybridlabor-api-aos/bind-audio-reactive.md
What bind_audio_reactive does on Aos
AI agents use bind_audio_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 bind_audio_reactive is rated Medium
This tool modifies the properties of a TouchDesigner component by linking it to audio input. It creates or updates parameter bindings, which is a reversible write operation. It does not delete data, execute arbitrary code, or involve financial transactions. Severity is medium because misconfiguration could affect a live visual performance system.
From the tool's definition 'Make a whole COMP react to the music in one call' — binds/configures audio reactivity parameters on a component
Attacks that exploit this kind of access
The rule that runs bind_audio_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 bind_audio_reactive, this is the rule to start with:
bind_audio_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 bind_audio_reactive call is checked against it from then on.
Questions about bind_audio_reactive
Make a whole COMP react to the music in one call — the core VJ move. Point. 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 bind_audio_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.
bind_audio_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 bind_audio_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 bind_audio_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.
bind_audio_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