This record as markdown: /tools/hybridlabor-api-aos/create-setlist-runner.md
What create_setlist_runner does on Aos
AI agents invoke create_setlist_runner 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_setlist_runner is rated High
This tool initiates and controls timed execution of a VJ setlist, orchestrating external audiovisual operations in a live performance context. It triggers active runtime behavior (playback control, scheduling) rather than merely writing static data. The blast radius is high because misuse could disrupt a live performance or cause unintended visual output on stage.
From the tool's definition 'wall-clock setlist player for rehearsed VJ shows' — triggers timed playback execution of a pre-arranged setlist, driving real-time visual output in TouchDesigner
Attacks that exploit this kind of access
The rule that runs create_setlist_runner 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_setlist_runner, this is the rule to start with:
create_setlist_runner 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 create_setlist_runner call is checked against it from then on.
Questions about create_setlist_runner
Layer-1 wall-clock setlist player for rehearsed VJ shows. Pass. 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 create_setlist_runner: 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_setlist_runner 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 create_setlist_runner 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_setlist_runner. 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_setlist_runner 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