create_pop_particle_system
Build a complete POP particle simulation (particle_pop → feedback_pop →
This record as markdown: /tools/hybridlabor-api-aos/create-pop-particle-system.md
What create_pop_particle_system does on Aos
AI agents use create_pop_particle_system 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_pop_particle_system is rated Medium
This tool constructs a particle simulation network within TouchDesigner, creating new nodes and connections. This is a Write operation (creating data/objects reversibly) with medium severity since misuse could clutter or corrupt a project network, but it does not execute arbitrary code or irreversibly destroy data.
From the tool's definition 'Build a complete POP particle simulation (particle_pop → feedback_pop →' — creates a new node network/simulation system in TouchDesigner
Attacks that exploit this kind of access
The rule that runs create_pop_particle_system 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_pop_particle_system, this is the rule to start with:
create_pop_particle_system 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_pop_particle_system call is checked against it from then on.
Questions about create_pop_particle_system
Build a complete POP particle simulation (particle_pop → feedback_pop →. 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_pop_particle_system: 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_pop_particle_system 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_pop_particle_system 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_pop_particle_system. 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_pop_particle_system 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