This record as markdown: /tools/hybridlabor-api-aos/morph-pack.md
What morph_pack does on Aos
AI agents use morph_pack 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 morph_pack is rated Medium
This is a Write operation because it creates/exports data in a structured format, but it operates on existing data rather than irreversibly deleting it. The severity is medium because exporting data could expose sensitive visual/artistic work or configurations, but it doesn't modify the original project or execute arbitrary code. It's reversible—the export can be deleted without affecting the source project.
From the tool's definition The tool name 'morph_pack' and description 'Export an existing create_preset_morph container' indicate it creates or generates a persistent export artifact (a pack file) from existing container data in TouchDesigner.
Attacks that exploit this kind of access
The rule that runs morph_pack 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 morph_pack, this is the rule to start with:
morph_pack 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 morph_pack call is checked against it from then on.
Questions about morph_pack
Export an existing create_preset_morph container. 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 morph_pack: 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.
morph_pack 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 morph_pack 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 morph_pack. 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.
morph_pack 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