image_to_particles
Turn any image (a file path or an existing TOP) into a GPU particle field: each particle
This record as markdown: /tools/io-github-pantani-tdmcp/image-to-particles.md
What image_to_particles does on tdmcp — TouchDesigner MCP server
AI agents invoke image_to_particles to trigger actions in tdmcp — TouchDesigner MCP server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why image_to_particles is rated High
This tool executes an operation in TouchDesigner that creates a GPU particle field from an image, which involves running GPU computations and modifying the live project network. It goes beyond a simple write (creating/modifying data) because it triggers active computation and external system operations.
From the tool's definition 'Turn any image (a file path or an existing TOP) into a GPU particle field: each particle' — triggers GPU-based particle system generation, executing a complex external operation in TouchDesigner that modifies the live project state
Attacks that exploit this kind of access
The rule that runs image_to_particles 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 image_to_particles, this is the rule to start with:
image_to_particles stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 image_to_particles call is checked against it from then on.
Questions about image_to_particles
Turn any image (a file path or an existing TOP) into a GPU particle field: each particle. It is categorised as a Execute tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for image_to_particles: 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.
image_to_particles is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the image_to_particles 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 image_to_particles. 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.
image_to_particles 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.
Across the catalogue