randomize_controls

Randomize a COMP

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/randomize-controls.md

WHAT IT DOES

What randomize_controls does on Aos

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

Randomizing a COMP involves writing new parameter values to a TouchDesigner component. This is a reversible modification (parameters can be reset or changed again), placing it in the Write category. The blast radius is medium since misuse could disrupt a live visual system, but the action is not irreversible.

From the tool's definition 'Randomize a COMP' — modifies component parameters by setting them to random values

Attacks that exploit this kind of access

RECOMMENDED RULE

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

randomize_controls Rate-limited

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

FAQ

Questions about randomize_controls

What does the randomize_controls tool do? +

Randomize a COMP. 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 randomize_controls? +

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

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

Can I rate-limit randomize_controls? +

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

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

randomize_controls 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

The MCP Attack Database →

Guides

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