create_stage_dashboard
Serve one unified live-performance cockpit from a Web Server DAT — a single responsive web page (phone + laptop) that combines a grid of cue-launch buttons (recall named cues from manage_cue on the target COMP), master faders bound to chosen parameters, a big PANIC button (toggles the target COMP
This record as markdown: /tools/hybridlabor-api-aos/create-stage-dashboard.md
What create_stage_dashboard does on Aos
AI agents use create_stage_dashboard 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_stage_dashboard is rated Medium
This tool creates a new Web Server DAT and builds a dashboard UI (web page) within TouchDesigner — a Write operation that creates and configures nodes/data in the project. The PANIC button and cue-launch functionality suggest high blast radius if misused during a live performance, as it could disrupt running visual systems.
From the tool's definition Serve one unified live-performance cockpit from a Web Server DAT — a single responsive web page that combines a grid of cue-launch buttons, master faders bound to chosen parameters, a big PANIC button
Attacks that exploit this kind of access
The rule that runs create_stage_dashboard 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_stage_dashboard, this is the rule to start with:
create_stage_dashboard 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 create_stage_dashboard call is checked against it from then on.
Questions about create_stage_dashboard
Serve one unified live-performance cockpit from a Web Server DAT — a single responsive web page (phone + laptop) that combines a grid of cue-launch buttons (recall named cues from manage_cue on the target COMP), master faders bound to chosen parameters, a big PANIC button (toggles the target COMP. 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 create_stage_dashboard: 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_stage_dashboard 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 create_stage_dashboard 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_stage_dashboard. 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_stage_dashboard 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