create_feedback_tunnel
Build a parameterized infinite-zoom/rotate feedback tunnel: a seed TOP is composited with its own fed-back, zoomed, rotated, and decayed frame each cook to produce a hypnotic inward-spiral tunnel. Four audio-bind-ready controls (Zoom, Rotate, HueShift, Decay) are exposed on the container for live...
This record as markdown: /tools/hybridlabor-api-aos/create-feedback-tunnel.md
What create_feedback_tunnel does on Aos
AI agents use create_feedback_tunnel 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_feedback_tunnel is rated Medium
This tool creates new nodes/networks in TouchDesigner (a Write operation), constructing a feedback tunnel with compositing and parameter controls. It does not execute arbitrary code or shell commands, and effects are reversible by deleting the created network. Severity is medium as it modifies the project structure and could clutter or interfere with existing network layouts if misused.
From the tool's definition Build a parameterized infinite-zoom/rotate feedback tunnel... Four audio-bind-ready controls... are exposed on the container for live performance
Attacks that exploit this kind of access
The rule that runs create_feedback_tunnel 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_feedback_tunnel, this is the rule to start with:
create_feedback_tunnel 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_feedback_tunnel call is checked against it from then on.
Questions about create_feedback_tunnel
Build a parameterized infinite-zoom/rotate feedback tunnel: a seed TOP is composited with its own fed-back, zoomed, rotated, and decayed frame each cook to produce a hypnotic inward-spiral tunnel. Four audio-bind-ready controls (Zoom, Rotate, HueShift, Decay) are exposed on the container for live performance. A built-in animated noise seed is used when no. 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_feedback_tunnel: 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_feedback_tunnel 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_feedback_tunnel 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_feedback_tunnel. 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_feedback_tunnel 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