apply_post_processing
Chain post-processing effects (bloom, glitch, rgb_split, vignette, etc.) onto an existing TOP, applied in the order given. Creates a new baseCOMP under
This record as markdown: /tools/hybridlabor-api-aos/apply-post-processing.md
What apply_post_processing does on Aos
AI agents use apply_post_processing 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 apply_post_processing is rated Medium
This tool creates or modifies the TouchDesigner project by adding new components and effect chains, which is a reversible write operation. It does not execute arbitrary code, delete data, or move financial resources.
From the tool's definition Tool 'apply_post_processing' creates a new baseCOMP under an existing TOP and chains effects onto it. The description explicitly states it 'Creates a new baseCOMP', indicating persistent creation of components in the project structure.
Attacks that exploit this kind of access
The rule that runs apply_post_processing 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 apply_post_processing, this is the rule to start with:
apply_post_processing 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 apply_post_processing call is checked against it from then on.
Questions about apply_post_processing
Chain post-processing effects (bloom, glitch, rgb_split, vignette, etc.) onto an existing TOP, applied in the order given. Creates a new 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 apply_post_processing: 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.
apply_post_processing 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 apply_post_processing 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 apply_post_processing. 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.
apply_post_processing 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