create_xy_pad
Build a draggable 2D (XY) gesture pad — a Container COMP whose pointer drag drives an x/y CHOP of normalized control channels, optionally remapped into ranges and bound by expression to target parameters (e.g. an effect
This record as markdown: /tools/io-github-pantani-tdmcp/create-xy-pad.md
What create_xy_pad does on tdmcp — TouchDesigner MCP server
AI agents use create_xy_pad 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_xy_pad is rated Medium
This tool creates and configures new UI components and parameter bindings in a TouchDesigner project. It is a Write operation because it creates reversible data structures (a Container COMP with control logic) and establishes parameter relationships. It does not execute arbitrary code (Execute), delete anything (Destructive), move money (Financial), or merely read data (Read).
From the tool's definition Tool creates a new UI component ('draggable 2D (XY) gesture pad — a Container COMP') and binds control channels to target parameters through expressions. Key verbs: 'Build', 'creates', 'drives', 'bound by expression'.
Attacks that exploit this kind of access
The rule that runs create_xy_pad 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_xy_pad, this is the rule to start with:
create_xy_pad 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_xy_pad call is checked against it from then on.
Questions about create_xy_pad
Build a draggable 2D (XY) gesture pad — a Container COMP whose pointer drag drives an x/y CHOP of normalized control channels, optionally remapped into ranges and bound by expression to target parameters (e.g. an effect. 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_xy_pad: 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_xy_pad 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_xy_pad 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_xy_pad. 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_xy_pad 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