apply_glsl_top_mapping
Build a self-contained GLSL TOP network from a pre-translated mapping (fragment + uniforms + channels + controls). Foundation primitive used by Shadertoy and ISF importers; also reachable directly for power users with a hand-translated fragment.
This record as markdown: /tools/io-github-pantani-tdmcp/apply-glsl-top-mapping.md
What apply_glsl_top_mapping does on tdmcp — TouchDesigner MCP server
AI agents invoke apply_glsl_top_mapping 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 apply_glsl_top_mapping is rated High
This tool compiles and runs arbitrary GLSL fragment shader code within TouchDesigner, creating an operational shader network. Executing user-supplied GPU programs can have significant side effects (resource exhaustion, driver crashes, visual system disruption), placing it firmly in Execute. It doesn't merely write static data — it deploys runnable code into a live visual environment.
From the tool's definition 'Build a self-contained GLSL TOP network from a pre-translated mapping (fragment + uniforms + channels + controls)' — executes GPU shader code (GLSL fragment) and constructs a live node network in TouchDesigner
Attacks that exploit this kind of access
The rule that runs apply_glsl_top_mapping 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 apply_glsl_top_mapping, this is the rule to start with:
apply_glsl_top_mapping 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 apply_glsl_top_mapping call is checked against it from then on.
Questions about apply_glsl_top_mapping
Build a self-contained GLSL TOP network from a pre-translated mapping (fragment + uniforms + channels + controls). Foundation primitive used by Shadertoy and ISF importers; also reachable directly for power users with a hand-translated fragment. 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 apply_glsl_top_mapping: 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.
apply_glsl_top_mapping 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 apply_glsl_top_mapping 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 apply_glsl_top_mapping. 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.
apply_glsl_top_mapping 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