This record as markdown: /tools/hybridlabor-api-aos/setup-tdableton.md
What setup_tdableton does on Aos
AI agents invoke setup_tdableton to trigger actions in Aos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why setup_tdableton is rated High
This tool establishes an external software bridge between TouchDesigner and Ableton Live, probing and configuring live connections. This constitutes executing external operations with side effects (network/IPC bridge setup, auto-probing of external software), going beyond a simple write. Misuse could disrupt live audio/visual performances or create persistent unwanted connections, giving it high severity.
From the tool's definition 'Wire up an Ableton Live bridge inside a tdmcp-managed container. Auto mode probes' — triggers external bridge setup and probing operations connecting TouchDesigner to Ableton Live
Attacks that exploit this kind of access
The rule that runs setup_tdableton 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 setup_tdableton, this is the rule to start with:
setup_tdableton stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 setup_tdableton call is checked against it from then on.
Questions about setup_tdableton
Wire up an Ableton Live bridge inside a tdmcp-managed container. Auto mode probes. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aos MCP server in PolicyLayer and add a rule for setup_tdableton: 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.
setup_tdableton is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the setup_tdableton 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 setup_tdableton. 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.
setup_tdableton 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