plan_visual
Turn a natural-language description of a visual you WANT into a build plan (which tool/recipe and nodes) — a dry run that creates nothing. Note: this does NOT inspect the current TouchDesigner project; to read existing nodes use get_td_nodes / get_td_topology / find_td_nodes.
This record as markdown: /tools/io-github-pantani-tdmcp/plan-visual.md
What plan_visual does on tdmcp — TouchDesigner MCP server
AI agents call plan_visual to retrieve information from tdmcp — TouchDesigner MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why plan_visual is rated Low
The tool explicitly states it performs a dry run and creates nothing. It takes a natural-language description and returns a plan (which tool/recipe and nodes to use), making it purely a read/query operation with no side effects. Misuse has minimal blast radius since no actual changes are made to the TouchDesigner project.
From the tool's definition 'a dry run that creates nothing' — the tool only generates a build plan from a natural-language description without modifying or creating any nodes or project state.
Attacks that exploit this kind of access
The rule that runs plan_visual 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 plan_visual, this is the rule to start with:
plan_visual is read-only, so it stays allowed. 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 plan_visual call is checked against it from then on.
Questions about plan_visual
Turn a natural-language description of a visual you WANT into a build plan (which tool/recipe and nodes) — a dry run that creates nothing. Note: this does NOT inspect the current TouchDesigner project; to read existing nodes use get_td_nodes / get_td_topology / find_td_nodes. It is categorised as a Read tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it retrieves data without modifying state.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for plan_visual: 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.
plan_visual is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the plan_visual 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 plan_visual. 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.
plan_visual 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