create_hand_gesture_bus
Build a stable MediaPipe-hands gesture bus for palm holograms, lasers, audio controls, and other hand-reactive visuals. Outputs a Null CHOP with debounced palm and pinch channels: palm_open, float_x/y, palm_size, pinch_active, pinch_power, scale_target, light_gain, and audio_level. Defaults to a ...
This record as markdown: /tools/io-github-pantani-tdmcp/create-hand-gesture-bus.md
What create_hand_gesture_bus does on tdmcp — TouchDesigner MCP server
AI agents use create_hand_gesture_bus to create or update resources in tdmcp — TouchDesigner MCP server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your tdmcp — TouchDesigner MCP server environment.
Why create_hand_gesture_bus is rated Medium
This tool creates a new node network/component in TouchDesigner (a Null CHOP with associated gesture processing chain). It constructs and writes new objects into the TouchDesigner project graph. No irreversible deletion occurs, no code is executed in an arbitrary shell sense, and no financial action is taken.
From the tool's definition Build a stable MediaPipe-hands gesture bus... Outputs a Null CHOP with debounced palm and pinch channels... Defaults to a synthetic two-hand source so it previews without a camera
Attacks that exploit this kind of access
The rule that runs create_hand_gesture_bus safely
PolicyLayer is an MCP gateway: it sits between your AI agents and tdmcp — TouchDesigner MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_hand_gesture_bus, this is the rule to start with:
create_hand_gesture_bus 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 tdmcp — TouchDesigner MCP server, apply this rule, and every create_hand_gesture_bus call is checked against it from then on.
Questions about create_hand_gesture_bus
Build a stable MediaPipe-hands gesture bus for palm holograms, lasers, audio controls, and other hand-reactive visuals. Outputs a Null CHOP with debounced palm and pinch channels: palm_open, float_x/y, palm_size, pinch_active, pinch_power, scale_target, light_gain, and audio_level. Defaults to a synthetic two-hand source so it previews without a camera; source=. It is categorised as a Write tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for create_hand_gesture_bus: 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 tdmcp — TouchDesigner MCP server. Nothing to install.
create_hand_gesture_bus 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_hand_gesture_bus 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_hand_gesture_bus. 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_hand_gesture_bus is provided by the tdmcp — TouchDesigner MCP server MCP server (@dpantani/tdmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.
This server
Across the catalogue