setup_hand_tracking

One-shot MediaPipe hand tracking from a webcam: loads the mediapipe-touchdesigner ENGINE (install with

SERVERtdmcp — TouchDesigner MCP server SOURCE@dpantani/tdmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pantani-tdmcp/setup-hand-tracking.md

WHAT IT DOES

What setup_hand_tracking does on tdmcp — TouchDesigner MCP server

AI agents invoke setup_hand_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.

RISK

Why setup_hand_tracking is rated High

This tool executes an external operation by loading a MediaPipe ENGINE component into TouchDesigner and activating webcam hardware. It triggers real system-level operations (hardware access, external library loading) whose effects depend on the environment. It is not purely destructive, financial, or a simple read/write — it initiates an active runtime process, placing it in Execute.

From the tool's definition 'One-shot MediaPipe hand tracking from a webcam: loads the mediapipe-touchdesigner ENGINE' — triggers loading an external engine component and activating webcam/hardware input

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs setup_hand_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_hand_tracking, this is the rule to start with:

setup_hand_tracking Rate-limited

setup_hand_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setup_hand_tracking": {
      "limits": [
        {
          "counter": "setup_hand_tracking_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every setup_hand_tracking call is checked against it from then on.

FAQ

Questions about setup_hand_tracking

What does the setup_hand_tracking tool do? +

One-shot MediaPipe hand tracking from a webcam: loads the mediapipe-touchdesigner ENGINE (install 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.

How do I enforce a policy on setup_hand_tracking? +

Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for setup_hand_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.

What risk level is setup_hand_tracking? +

setup_hand_tracking is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit setup_hand_tracking? +

Yes. Add a rate_limit block to the setup_hand_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.

How do I block setup_hand_tracking completely? +

Set action: deny in the PolicyLayer policy for setup_hand_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.

What MCP server provides setup_hand_tracking? +

setup_hand_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.

KEEP EXPLORING

More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.

This server

All 334 tdmcp — TouchDesigner MCP server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →