create_pose_tracking
Set up full-body pose tracking — the foundation for body-reactive visuals (the camera/skeleton counterpart to extract_audio_features). Produces a canonical pose CHOP (33 MediaPipe landmarks as samples, channels tx/ty/tz/confidence) plus a
This record as markdown: /tools/hybridlabor-api-aos/create-pose-tracking.md
What create_pose_tracking does on Aos
AI agents use create_pose_tracking 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_pose_tracking is rated Medium
This tool sets up a pose tracking pipeline within TouchDesigner, creating new CHOPs and associated components. It creates/configures data rather than reading existing state, executing arbitrary code, or performing destructive/financial actions. Severity is medium because misconfiguration could disrupt an existing project's network layout, but effects are reversible.
From the tool's definition 'Set up full-body pose tracking' and 'Produces a canonical pose CHOP' — creates and configures new nodes/operators in the TouchDesigner project
Attacks that exploit this kind of access
The rule that runs create_pose_tracking 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_pose_tracking, this is the rule to start with:
create_pose_tracking 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_pose_tracking call is checked against it from then on.
Questions about create_pose_tracking
Set up full-body pose tracking — the foundation for body-reactive visuals (the camera/skeleton counterpart to extract_audio_features). Produces a canonical pose CHOP (33 MediaPipe landmarks as samples, channels tx/ty/tz/confidence) plus a. 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_pose_tracking: 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_pose_tracking 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_pose_tracking 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_pose_tracking. 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_pose_tracking 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