create_pose_skeleton
Render a live stick-figure skeleton from full-body pose tracking — the classic MediaPipe body-tracking look: glowing lines connecting the 33 landmarks (shoulders, elbows, wrists, hips, knees, ankles) drawn by a Line MAT and rendered to a Null TOP you can composite or post-process. Source defaults...
This record as markdown: /tools/hybridlabor-api-aos/create-pose-skeleton.md
What create_pose_skeleton does on Aos
AI agents use create_pose_skeleton 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_skeleton is rated Medium
This tool creates and configures a network of TouchDesigner nodes (operators) to render a pose skeleton. It writes/creates new components and wires them together in the project. There is no irreversible deletion, code execution in an arbitrary sense, or financial action. The blast radius is medium because it modifies the live TouchDesigner project network, but changes are reversible by removing the created nodes.
From the tool's definition 'Render a live stick-figure skeleton from full-body pose tracking' — creates nodes/operators in TouchDesigner (Line MAT, Null TOP) and builds a visual pipeline; 'it builds and previews instantly'
Attacks that exploit this kind of access
The rule that runs create_pose_skeleton 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_skeleton, this is the rule to start with:
create_pose_skeleton 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_skeleton call is checked against it from then on.
Questions about create_pose_skeleton
Render a live stick-figure skeleton from full-body pose tracking — the classic MediaPipe body-tracking look: glowing lines connecting the 33 landmarks (shoulders, elbows, wrists, hips, knees, ankles) drawn by a Line MAT and rendered to a Null TOP you can composite or post-process. Source defaults to a SYNTHETIC animated pose so it builds and previews instantly with no camera and no plugin; switch to. 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_skeleton: 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_skeleton 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_skeleton 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_skeleton. 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_skeleton 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