create_blob_reactive
Build a blob-position-tracking chain that drives parameters from the POSITIONS of multiple objects/hands in a camera (or a TOP) — the per-blob counterpart to create_motion_reactive
This record as markdown: /tools/hybridlabor-api-aos/create-blob-reactive.md
What create_blob_reactive does on Aos
AI agents use create_blob_reactive 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_blob_reactive is rated Medium
This tool creates (builds) a new node chain/network in TouchDesigner that tracks blob positions and drives parameters. It is a creative/constructive operation that adds new nodes and connections to the project, making it a Write operation. Misuse could clutter or corrupt a TouchDesigner project but is generally reversible by deleting the created nodes.
From the tool's definition 'Build a blob-position-tracking chain that drives parameters' — creates a new processing chain/network in TouchDesigner
Attacks that exploit this kind of access
The rule that runs create_blob_reactive 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_blob_reactive, this is the rule to start with:
create_blob_reactive 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_blob_reactive call is checked against it from then on.
Questions about create_blob_reactive
Build a blob-position-tracking chain that drives parameters from the POSITIONS of multiple objects/hands in a camera (or a TOP) — the per-blob counterpart to create_motion_reactive. 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_blob_reactive: 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_blob_reactive 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_blob_reactive 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_blob_reactive. 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_blob_reactive 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