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

create_control_surface

Build a playable performance panel (a Container COMP of visual widgets) for live use, beyond the parameter dialog: vertical faders that drive parameters, and buttons that recall or morph to named cues (from manage_cue). Open the container in Perform/Panel mode for a touchable surface — faders mov...

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-control-surface.md

What create_control_surface does on Aos

AI agents use create_control_surface 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_control_surface is rated Medium

This tool creates a new UI component (Container COMP) in the TouchDesigner project — a reversible write/create operation. While it can trigger scene changes at runtime, its primary function is constructing the control surface widget. The live-use firing of cues is a secondary runtime behavior, not an irreversible destructive or financial action.

From the tool's definition 'Build a playable performance panel (a Container COMP of visual widgets)' and 'faders move their parameters, cue buttons fire scenes'

Questions about create_control_surface

What does the create_control_surface tool do? +

Build a playable performance panel (a Container COMP of visual widgets) for live use, beyond the parameter dialog: vertical faders that drive parameters, and buttons that recall or morph to named cues (from manage_cue). Open the container in Perform/Panel mode for a touchable surface — faders move their parameters, cue buttons fire scenes (instantly or with a crossfade). 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_control_surface? +

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

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

Can I rate-limit create_control_surface? +

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

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

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