create_chrome_blobs

Builds a liquid-chrome / Y2K metaball generator: an animated Noise TOP (or external source) is blurred, thresholded into soft blobs, then a GLSL TOP renders a procedural environment-map chrome look (greyscale ramp + moving specular highlight) with 5 metal tints and 4 background modes. Creates a s...

Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pantani-tdmcp/create-chrome-blobs.md

What create_chrome_blobs does on tdmcp — TouchDesigner MCP server

AI agents use create_chrome_blobs 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_chrome_blobs is rated Medium

This tool creates and configures a new TouchDesigner component (baseCOMP) with internal nodes, shader mappings, and parameter controls. While it modifies the project state by adding components and parameters, these changes are reversible (the component can be deleted or modified). This is a creative/constructive operation rather than destructive.

From the tool's definition Creates a self-contained baseCOMP with exposed parameters and visual effects setup. Keywords: 'Builds', 'Creates', 'renders', 'exposed...controls' indicate creation and modification of TouchDesigner components and parameters.

Questions about create_chrome_blobs

What does the create_chrome_blobs tool do? +

Builds a liquid-chrome / Y2K metaball generator: an animated Noise TOP (or external source) is blurred, thresholded into soft blobs, then a GLSL TOP renders a procedural environment-map chrome look (greyscale ramp + moving specular highlight) with 5 metal tints and 4 background modes. Creates a self-contained baseCOMP with Speed, Blob_Count, Metal_Color, and Background controls exposed on the container. 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.

How do I enforce a policy on create_chrome_blobs? +

Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for create_chrome_blobs: 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.

What risk level is create_chrome_blobs? +

create_chrome_blobs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_chrome_blobs? +

Yes. Add a rate_limit block to the create_chrome_blobs 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.

How do I block create_chrome_blobs completely? +

Set action: deny in the PolicyLayer policy for create_chrome_blobs. 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.

What MCP server provides create_chrome_blobs? +

create_chrome_blobs 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of tdmcp — TouchDesigner MCP server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.