connect_comfyui
Bridge a running ComfyUI server: drops the TDComfyUI .tox if installed, otherwise builds a stock webclientDAT skeleton. The container exposes a Null TOP at <container>/out as the downstream output.
This record as markdown: /tools/io-github-pantani-tdmcp/connect-comfyui.md
What connect_comfyui does on tdmcp — TouchDesigner MCP server
AI agents use connect_comfyui 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 connect_comfyui is rated Medium
This tool modifies the TouchDesigner project structure by either removing an existing component ('drops the TDComfyUI .tox') or creating new ones ('builds a stock webclientDAT skeleton'). These are reversible Write operations (components can be deleted or rebuilt), not Destructive ones, since TouchDesigner projects can typically undo or recover from such changes.
From the tool's definition Tool description states it 'drops the TDComfyUI .tox if installed' and 'builds a stock webclientDAT skeleton', indicating irreversible component installation/replacement and architectural modification of the TouchDesigner project.
Attacks that exploit this kind of access
The rule that runs connect_comfyui 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 connect_comfyui, this is the rule to start with:
connect_comfyui 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 connect_comfyui call is checked against it from then on.
Questions about connect_comfyui
Bridge a running ComfyUI server: drops the TDComfyUI .tox if installed, otherwise builds a stock webclientDAT skeleton. The container exposes a Null TOP at <container>/out as the downstream output. 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 connect_comfyui: 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.
connect_comfyui 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 connect_comfyui 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 connect_comfyui. 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.
connect_comfyui 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