create_keyer
Composite a keyed performer, logo, or any source over a background visual — the green-screen / chroma-key / matte tool for installations and live camera work. Creates a self-contained baseCOMP under
This record as markdown: /tools/hybridlabor-api-aos/create-keyer.md
What create_keyer does on Aos
AI agents use create_keyer 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_keyer is rated Medium
This tool creates new compositing components (a baseCOMP) in TouchDesigner, which modifies the project state by adding new visual processing nodes. This is a reversible write operation—the created component can be deleted or modified. It does not execute arbitrary code, delete existing assets, or move money, making Write the appropriate category.
From the tool's definition Tool description states it "Creates a self-contained baseCOMP" which indicates creation of new components/objects in TouchDesigner. The verb 'Composite' and 'Creates' indicate data/asset generation rather than read-only operations.
Attacks that exploit this kind of access
The rule that runs create_keyer 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_keyer, this is the rule to start with:
create_keyer 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_keyer call is checked against it from then on.
Questions about create_keyer
Composite a keyed performer, logo, or any source over a background visual — the green-screen / chroma-key / matte tool for installations and live camera work. Creates a self-contained baseCOMP under. 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_keyer: 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_keyer 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_keyer 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_keyer. 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_keyer 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