This record as markdown: /tools/hybridlabor-api-aos/create-video-player.md
What create_video_player does on Aos
AI agents use create_video_player 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_video_player is rated Medium
This tool creates a new video player component within TouchDesigner, which is a reversible data/project modification. It does not execute arbitrary code on the system, delete data, or perform financial operations. While it modifies the TouchDesigner project state, this is a standard Write operation (create).
From the tool's definition Tool name 'create_video_player' and description 'Build a movie/clip player inside a new' indicates creation of a new component/project element within TouchDesigner.
Attacks that exploit this kind of access
The rule that runs create_video_player 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_video_player, this is the rule to start with:
create_video_player 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_video_player call is checked against it from then on.
Questions about create_video_player
Build a movie/clip player inside a new. 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_video_player: 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_video_player 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_video_player 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_video_player. 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_video_player 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