create_prob_sequencer
Build a Markov-chain step sequencer. On each beat boundary the COMP transitions from the current state to a next state sampled from the per-state weighted-transition table. Outputs two CHOP channels:
This record as markdown: /tools/hybridlabor-api-aos/create-prob-sequencer.md
What create_prob_sequencer does on Aos
AI agents use create_prob_sequencer 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.
Why create_prob_sequencer is rated Medium
This tool creates a new node/component in a TouchDesigner project (a probabilistic step sequencer). It is a Write operation — it builds and instantiates a new object in the visual programming environment. There is no code execution, deletion, or financial impact. Misuse could clutter or disrupt a project network but effects are reversible.
From the tool's definition 'Build a Markov-chain step sequencer' — creates a new sequencer component (COMP) with CHOP outputs in TouchDesigner
Attacks that exploit this kind of access
The rule that runs create_prob_sequencer 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_prob_sequencer, this is the rule to start with:
create_prob_sequencer 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every create_prob_sequencer call is checked against it from then on.
Questions about create_prob_sequencer
Build a Markov-chain step sequencer. On each beat boundary the COMP transitions from the current state to a next state sampled from the per-state weighted-transition table. Outputs two CHOP channels:. 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.
Register the Aos MCP server in PolicyLayer and add a rule for create_prob_sequencer: 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.
create_prob_sequencer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_prob_sequencer 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 create_prob_sequencer. 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.
create_prob_sequencer 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.
More on Aos, and thousands of servers like it.
This server
Across the catalogue