create_chrome_blobs

SERVERAos SOURCE@hybridlabor-api/aos

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/hybridlabor-api-aos/create-chrome-blobs.md

WHAT IT DOES

What create_chrome_blobs does on Aos

AI agents use create_chrome_blobs to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.

RISK

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_chrome_blobs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_chrome_blobs, this is the rule to start with:

create_chrome_blobs Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_chrome_blobs": {
      "limits": [
        {
          "counter": "create_chrome_blobs_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every create_chrome_blobs call is checked against it from then on.

FAQ

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 Aos 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 Aos 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 Aos. 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 Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →