create_cubemap_dome
Render a true cube-map dome master — the higher-fidelity follow-up to create_dome_output (which only warps a flat equirectangular source). A 3D scene is rendered by a Render TOP in cube-map mode (rendermode
This record as markdown: /tools/hybridlabor-api-aos/create-cubemap-dome.md
What create_cubemap_dome does on Aos
AI agents use create_cubemap_dome 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_cubemap_dome is rated Medium
This tool creates a new cube-map dome rendering setup within TouchDesigner, which is a Write operation (creating and configuring nodes/outputs). It does not delete data, execute arbitrary code, or involve financial transactions. The severity is medium because misuse could create unintended nodes or alter a project's network, but effects are reversible.
From the tool's definition 'Render a true cube-map dome master' — creates a new rendering output/node configuration in TouchDesigner; described as a 'follow-up' that sets up a Render TOP in cube-map mode, indicating creation/configuration of new nodes
Attacks that exploit this kind of access
The rule that runs create_cubemap_dome 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_cubemap_dome, this is the rule to start with:
create_cubemap_dome 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_cubemap_dome call is checked against it from then on.
Questions about create_cubemap_dome
Render a true cube-map dome master — the higher-fidelity follow-up to create_dome_output (which only warps a flat equirectangular source). A 3D scene is rendered by a Render TOP in cube-map mode (rendermode. 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_cubemap_dome: 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_cubemap_dome 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_cubemap_dome 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_cubemap_dome. 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_cubemap_dome 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