create_hand_ableton_mapper
Build a MediaPipe-hands to TDAbleton TDA_Mapper performance control network. It outputs map1=left pinch, map2=right pinch, map3=left wrist roll, map4=right wrist roll, creates a skeleton overlay with star joints plus the thumb-index line, and optionally relinks an existing TDA_Mapper to the gener...
This record as markdown: /tools/io-github-pantani-tdmcp/create-hand-ableton-mapper.md
What create_hand_ableton_mapper does on tdmcp — TouchDesigner MCP server
AI agents use create_hand_ableton_mapper 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_ableton_mapper is rated Medium
This tool creates and wires up a network of nodes/components in TouchDesigner (a visual programming environment), creating new operators and optionally relinking existing ones. It modifies the project state by adding new components and connections, which is a reversible write operation. There is no execution of arbitrary code, deletion of data, or financial transaction involved.
From the tool's definition Build a MediaPipe-hands to TDAbleton TDA_Mapper performance control network...creates a skeleton overlay...optionally relinks an existing TDA_Mapper to the generated mapper_send CHOP
Attacks that exploit this kind of access
The rule that runs create_hand_ableton_mapper 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_ableton_mapper, this is the rule to start with:
create_hand_ableton_mapper 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_ableton_mapper call is checked against it from then on.
Questions about create_hand_ableton_mapper
Build a MediaPipe-hands to TDAbleton TDA_Mapper performance control network. It outputs map1=left pinch, map2=right pinch, map3=left wrist roll, map4=right wrist roll, creates a skeleton overlay with star joints plus the thumb-index line, and optionally relinks an existing TDA_Mapper to the generated mapper_send CHOP. Uses TDAbleton directly; AbletonMCP is not required. 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_ableton_mapper: 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_ableton_mapper 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_ableton_mapper 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_ableton_mapper. 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_ableton_mapper 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