rebuild_network
Reconstruct a live network inside a COMP from a serialize_network spec — the REBUILD half of a git-diffable round-trip. Takes a JSON spec of nodes (name, operator type, parameters as constants/expressions/binds, inbound wires by name, optional x/y) and, in one pass, creates every node, applies it...
This record as markdown: /tools/hybridlabor-api-aos/rebuild-network.md
What rebuild_network does on Aos
AI agents invoke rebuild_network to trigger actions in Aos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why rebuild_network is rated High
This tool executes a full network reconstruction in a live system: it creates nodes, applies parameters/expressions, and wires connections. It's not merely writing data to a database but triggering real-time execution and topology changes in a live visual programming environment. The blast radius is high because a malformed or malicious spec could corrupt or destabilize the entire live TouchDesigner project network.
From the tool's definition 'Reconstruct a live network inside a COMP' — creates every node, applies parameters and expressions, then wires inputs; operates on a live TouchDesigner environment from a JSON spec
Attacks that exploit this kind of access
The rule that runs rebuild_network 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 rebuild_network, this is the rule to start with:
rebuild_network stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 rebuild_network call is checked against it from then on.
Questions about rebuild_network
Reconstruct a live network inside a COMP from a serialize_network spec — the REBUILD half of a git-diffable round-trip. Takes a JSON spec of nodes (name, operator type, parameters as constants/expressions/binds, inbound wires by name, optional x/y) and, in one pass, creates every node, applies its parameters and expressions, then wires inputs by resolving each. It is categorised as a Execute tool in the Aos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aos MCP server in PolicyLayer and add a rule for rebuild_network: 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.
rebuild_network is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rebuild_network 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 rebuild_network. 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.
rebuild_network 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