This record as markdown: /tools/hybridlabor-api-aos/build-pop-chain.md
What build_pop_chain does on Aos
AI agents invoke build_pop_chain to trigger actions in Aos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why build_pop_chain is rated High
This tool executes a series of computational operations on 3D geometry in TouchDesigner's visual pipeline. While it does not delete data or move money, it triggers real-time processing and rendering effects that are non-trivial to undo and depend entirely on user-provided arguments. Misconfiguration could cause resource exhaustion, unintended visual artifacts, or cascading effects in a live visual system.
From the tool's definition 'build_pop_chain' is a declarative builder for an ordered POP (Point OPerator) chain in TouchDesigner. POPs are operators that process geometry/point data and trigger external operations (rendering, computation, simulation).
Attacks that exploit this kind of access
The rule that runs build_pop_chain 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 build_pop_chain, this is the rule to start with:
build_pop_chain stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 build_pop_chain call is checked against it from then on.
Questions about build_pop_chain
Declarative Layer-2 builder for an ordered POP (Point OPerator) chain. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aos MCP server in PolicyLayer and add a rule for build_pop_chain: 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.
build_pop_chain is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_pop_chain 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 build_pop_chain. 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.
build_pop_chain 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