multipass_3d_depth
Build a renderable 3D scene with depth cues that read on stage: a Geometry COMP holding the chosen primitive (sphere/box/torus/grid), a Camera, a Light, and a Render TOP beauty pass, output as a Null — like create_3d_scene but with an optional Screen-Space Ambient Occlusion (SSAO) pass for contac...
This record as markdown: /tools/hybridlabor-api-aos/multipass-3d-depth.md
What multipass_3d_depth does on Aos
AI agents use multipass_3d_depth 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 multipass_3d_depth is rated Medium
This tool creates and wires together multiple TouchDesigner nodes (Geometry COMP, Camera, Light, Render TOP, SSAO TOP, Depth TOP, Null outputs) in a project network. It constructs/writes new nodes and connections into the TouchDesigner environment, which is a reversible write operation (nodes can be deleted). It does not execute arbitrary code, delete data, or involve financial transactions.
From the tool's definition Build a renderable 3D scene... a Geometry COMP holding the chosen primitive, a Camera, a Light, and a Render TOP beauty pass... an optional Screen-Space Ambient Occlusion (SSAO) pass... and an optional Depth TOP output
Attacks that exploit this kind of access
The rule that runs multipass_3d_depth 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 multipass_3d_depth, this is the rule to start with:
multipass_3d_depth 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 multipass_3d_depth call is checked against it from then on.
Questions about multipass_3d_depth
Build a renderable 3D scene with depth cues that read on stage: a Geometry COMP holding the chosen primitive (sphere/box/torus/grid), a Camera, a Light, and a Render TOP beauty pass, output as a Null — like create_3d_scene but with an optional Screen-Space Ambient Occlusion (SSAO) pass for contact shadows, and an optional Depth TOP output. The SSAO TOP is wired directly after the Render TOP (it needs the depth buffer — no TOP between them) and combined with the color. When expose_depth is on, a Depth TOP resolves the same render into a depth map exposed as a second Null (. 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 multipass_3d_depth: 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.
multipass_3d_depth 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 multipass_3d_depth 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 multipass_3d_depth. 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.
multipass_3d_depth 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