create_body_bubbles
Create a MediaPipe-ready interactive bubble installation over the live camera: a detected open palm emits soap-like bubbles, body and hand landmarks act as soft colliders that can bat or lift them, a visible body contour is rendered in the same output so the interaction reads clearly, bubbles sta...
This record as markdown: /tools/io-github-pantani-tdmcp/create-body-bubbles.md
What create_body_bubbles does on tdmcp — TouchDesigner MCP server
AI agents invoke create_body_bubbles to trigger actions in tdmcp — TouchDesigner MCP server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why create_body_bubbles is rated High
This tool constructs and executes a complex real-time system inside TouchDesigner — spawning nodes, running physics scripts, and accessing the live camera feed. It goes well beyond a simple Write (creating data), as it triggers active computation via a Script CHOP and builds an operational interactive installation.
From the tool's definition Builds a self-contained Base COMP with a Script CHOP physics solve; creates a MediaPipe-ready interactive bubble installation over the live camera
Attacks that exploit this kind of access
The rule that runs create_body_bubbles 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_body_bubbles, this is the rule to start with:
create_body_bubbles stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_body_bubbles call is checked against it from then on.
Questions about create_body_bubbles
Create a MediaPipe-ready interactive bubble installation over the live camera: a detected open palm emits soap-like bubbles, body and hand landmarks act as soft colliders that can bat or lift them, a visible body contour is rendered in the same output so the interaction reads clearly, bubbles stay inside the screen box, settle on the lower floor, and pop/fade after a configurable lifetime (default 30 seconds). By default it keeps the bubble count low and disables pose-wrist emission, so bubbles are created only by an open palm. Builds a self-contained Base COMP with a Script CHOP physics solver, Script SOP bubble outlines, Script SOP body contour, camera-background composite, Geometry/Render/Null TOP output, a frame cooker, and live controls for emission rate, gravity, drag, buoyancy, skeleton impulse, bubble repulsion, tracking smoothing, body radius, body contour, camera opacity, lifetime, and bounce. Provide hand_chop_path from setup_hand_tracking and body_chop_path from setup_body_tracking/create_pose_tracking for full interaction. It is categorised as a Execute tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for create_body_bubbles: 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_body_bubbles is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_body_bubbles 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_body_bubbles. 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_body_bubbles 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.
Across the catalogue