setup_body_tracking
One-shot body tracking from a webcam: loads the free mediapipe-touchdesigner ENGINE (install it first with
This record as markdown: /tools/io-github-pantani-tdmcp/setup-body-tracking.md
What setup_body_tracking does on tdmcp — TouchDesigner MCP server
AI agents invoke setup_body_tracking 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 setup_body_tracking is rated High
This tool actively loads an external ENGINE (mediapipe-touchdesigner), configures webcam access, and sets up real-time body tracking. It triggers external operations — loading third-party software, accessing hardware (webcam), and running a continuous tracking process. This goes beyond writing config data; it executes a pipeline that depends on arguments and environment.
From the tool's definition 'One-shot body tracking from a webcam: loads the free mediapipe-touchdesigner ENGINE' — the tool installs/loads an external engine component and sets up active tracking operations in TouchDesigner, triggering external operations with real-world effects
Attacks that exploit this kind of access
The rule that runs setup_body_tracking 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 setup_body_tracking, this is the rule to start with:
setup_body_tracking 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 setup_body_tracking call is checked against it from then on.
Questions about setup_body_tracking
One-shot body tracking from a webcam: loads the free mediapipe-touchdesigner ENGINE (install it first with. 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 setup_body_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 tdmcp — TouchDesigner MCP server. Nothing to install.
setup_body_tracking 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 setup_body_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 setup_body_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.
setup_body_tracking 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