post_passes_3d
Compose a chain of 3D-aware post-processing passes (SSAO, SSR, DOF, motion blur) inside a new baseCOMP. Each pass is a glslTOP with companion textDAT that samples color + depth + (optional) normal/velocity AOVs from selectTOPs. Passes run in fixed order SSAO → SSR → DOF → MB and emit a final null...
This record as markdown: /tools/hybridlabor-api-aos/post-passes-3d.md
What post_passes_3d does on Aos
AI agents use post_passes_3d 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 post_passes_3d is rated Medium
This tool creates new nodes and structures (baseCOMP, glslTOP, textDAT, selectTOPs, null TOP) inside a TouchDesigner project. It is a Write operation — constructing/composing a network of operators — rather than executing arbitrary code or destroying existing data. The blast radius is medium since it modifies the project network but in a reversible and scoped manner.
From the tool's definition Compose a chain of 3D-aware post-processing passes... inside a new baseCOMP. Each pass is a glslTOP with companion textDAT... Passes run in fixed order... and emit a final null TOP
Attacks that exploit this kind of access
The rule that runs post_passes_3d 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 post_passes_3d, this is the rule to start with:
post_passes_3d 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 post_passes_3d call is checked against it from then on.
Questions about post_passes_3d
Compose a chain of 3D-aware post-processing passes (SSAO, SSR, DOF, motion blur) inside a new baseCOMP. Each pass is a glslTOP with companion textDAT that samples color + depth + (optional) normal/velocity AOVs from selectTOPs. Passes run in fixed order SSAO → SSR → DOF → MB and emit a final null TOP (. 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 post_passes_3d: 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.
post_passes_3d 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 post_passes_3d 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 post_passes_3d. 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.
post_passes_3d 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