create_kaleidoscope
Wrap a source in a kaleidoscope / radial-mirror symmetry effect — a signature VJ look. Folds the image into N identical mirrored wedges around a centre, with live Segments / Rotation / Zoom / Center controls. Creates a new baseCOMP under
This record as markdown: /tools/io-github-pantani-tdmcp/create-kaleidoscope.md
What create_kaleidoscope does on tdmcp — TouchDesigner MCP server
AI agents use create_kaleidoscope 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_kaleidoscope is rated Medium
This tool creates and modifies visual components within TouchDesigner by generating a new baseCOMP (composite component) with kaleidoscope effects and associated controls. This is a reversible, non-destructive creation/modification action. It does not execute arbitrary code (Execute), delete anything (Destructive), involve financial transactions (Financial), or retrieve data passively (Read).
From the tool's definition The tool description states it 'Creates a new baseCOMP under' (incomplete but indicates creation). It 'Wrap[s] a source' and establishes new parameters ('Segments / Rotation / Zoom / Center controls'), all of which are creative modifications to the…
Attacks that exploit this kind of access
The rule that runs create_kaleidoscope 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_kaleidoscope, this is the rule to start with:
create_kaleidoscope 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_kaleidoscope call is checked against it from then on.
Questions about create_kaleidoscope
Wrap a source in a kaleidoscope / radial-mirror symmetry effect — a signature VJ look. Folds the image into N identical mirrored wedges around a centre, with live Segments / Rotation / Zoom / Center controls. Creates a new baseCOMP under. 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_kaleidoscope: 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_kaleidoscope 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_kaleidoscope 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_kaleidoscope. 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_kaleidoscope 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