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

create_sidechain_pump

EXPERIMENTAL — One-call

SERVERAos SOURCE@hybridlabor-api/aos
High RISK CLASS
Category Execute
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-sidechain-pump.md

What create_sidechain_pump does on Aos

AI agents invoke create_sidechain_pump 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 create_sidechain_pump is rated High

The tool appears to create and connect multiple TouchDesigner operators to set up a sidechain pump effect in one call. This spans Write (creating nodes) and Execute (triggering live visual/audio system changes). Since it operates on a live visual system and the description is nearly empty ('EXPERIMENTAL — One-call' is all we have), confidence is lowered.

From the tool's definition 'EXPERIMENTAL — One-call' and the name 'create_sidechain_pump' suggest triggering an audio-reactive sidechain pumping effect in TouchDesigner, creating nodes/operators and wiring them together

Questions about create_sidechain_pump

What does the create_sidechain_pump tool do? +

EXPERIMENTAL — One-call. 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.

How do I enforce a policy on create_sidechain_pump? +

Register the Aos MCP server in PolicyLayer and add a rule for create_sidechain_pump: 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_sidechain_pump? +

create_sidechain_pump is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_sidechain_pump? +

Yes. Add a rate_limit block to the create_sidechain_pump 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_sidechain_pump completely? +

Set action: deny in the PolicyLayer policy for create_sidechain_pump. 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_sidechain_pump? +

create_sidechain_pump 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.

// 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.