New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

create_decks

Build a DJ-style VJ mixer. Without decks[], it preserves the legacy A/B Cross TOP mixer with GainA/GainB controls. With decks[], it builds a 2-8 deck mixer: every deck pulls a source TOP (or a test source) through gain and FX-send Level TOPs, decks 3+ blend into a running Cross TOP chain, a Switc...

SERVERAos SOURCE@hybridlabor-api/aos
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/create-decks.md

What create_decks does on Aos

AI agents use create_decks 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_decks is rated Medium

This tool creates and modifies TouchDesigner network structures (TOPs, controls, buses) that compose a VJ mixer system. It does not execute arbitrary code or shell commands (Execute), does not irreversibly delete data (Destructive), does not involve financial transactions (Financial), and primarily constructs/modifies visual processing chains.

From the tool's definition Tool description states it 'Build[s] a DJ-style VJ mixer' and 'builds a 2-8 deck mixer' with multiple components (gain controls, FX-send levels, Switch TOP, Cross TOP, Null output).

Risk signalsBulk/mass operation — affects multiple targets

Questions about create_decks

What does the create_decks tool do? +

Build a DJ-style VJ mixer. Without decks[], it preserves the legacy A/B Cross TOP mixer with GainA/GainB controls. With decks[], it builds a 2-8 deck mixer: every deck pulls a source TOP (or a test source) through gain and FX-send Level TOPs, decks 3+ blend into a running Cross TOP chain, a Switch TOP provides hard transition cuts, a final Cross TOP blends program vs cut, and an additive FX-send bus returns per-deck sends into the master. Output is a Null ready for post-processing or setup_output. 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.

How do I enforce a policy on create_decks? +

Register the Aos MCP server in PolicyLayer and add a rule for create_decks: 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.

What risk level is create_decks? +

create_decks is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_decks? +

Yes. Add a rate_limit block to the create_decks 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.

How do I block create_decks completely? +

Set action: deny in the PolicyLayer policy for create_decks. 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.

What MCP server provides create_decks? +

create_decks 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Aos's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.