apply_lut

Apply a colour Look-Up Table (LUT) to an existing TOP inside a self-contained

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/apply-lut.md

WHAT IT DOES

What apply_lut does on Aos

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

This tool modifies the appearance/color properties of an existing TouchDesigner TOP by applying a LUT, which is a reversible transformation of visual data. It does not delete data (hence not Destructive), does not execute arbitrary code (hence not Execute), and does not create new data structures (borderline Write/Read, but application of a LUT is a modification operation).

From the tool's definition Tool description states 'Apply a colour Look-Up Table (LUT) to an existing TOP' — this modifies visual rendering properties of an existing component. The verb 'apply' indicates a configuration change to a TOP (Texture Operator) object.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs apply_lut 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 apply_lut, this is the rule to start with:

apply_lut Rate-limited

apply_lut 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": {
    "apply_lut": {
      "limits": [
        {
          "counter": "apply_lut_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 apply_lut call is checked against it from then on.

FAQ

Questions about apply_lut

What does the apply_lut tool do? +

Apply a colour Look-Up Table (LUT) to an existing TOP inside a self-contained. 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 apply_lut? +

Register the Aos MCP server in PolicyLayer and add a rule for apply_lut: 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 apply_lut? +

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

Can I rate-limit apply_lut? +

Yes. Add a rate_limit block to the apply_lut 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 apply_lut completely? +

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

apply_lut 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

binary_patch_apply on 010 Editor → The MCP Attack Database →

Guides

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