create_reaction_diffusion
Build a Gray-Scott reaction-diffusion GPU simulation as a ready-to-use visual system.
This record as markdown: /tools/hybridlabor-api-aos/create-reaction-diffusion.md
What create_reaction_diffusion does on Aos
AI agents use create_reaction_diffusion 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_reaction_diffusion is rated Medium
This tool creates a new GPU simulation system within TouchDesigner. It is a Write operation because it constructs and adds new nodes/networks to the project. It is reversible in that the created nodes can be deleted. Severity is medium because misuse could clutter or corrupt a project's node graph, but it does not execute arbitrary code or irreversibly destroy data.
From the tool's definition 'Build a Gray-Scott reaction-diffusion GPU simulation as a ready-to-use visual system' — creates a new visual system/node network in TouchDesigner
Attacks that exploit this kind of access
The rule that runs create_reaction_diffusion 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_reaction_diffusion, this is the rule to start with:
create_reaction_diffusion 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_reaction_diffusion call is checked against it from then on.
Questions about create_reaction_diffusion
Build a Gray-Scott reaction-diffusion GPU simulation as a ready-to-use visual system. 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_reaction_diffusion: 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_reaction_diffusion 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_reaction_diffusion 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_reaction_diffusion. 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_reaction_diffusion 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