export_palette_component
Save a COMP as a .tox into TouchDesigner
This record as markdown: /tools/hybridlabor-api-aos/export-palette-component.md
What export_palette_component does on Aos
AI agents use export_palette_component 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 export_palette_component is rated Medium
This is a Write operation because it creates/exports a new file (reversible via deletion). It does not execute arbitrary code on the system, merely serializes a TouchDesigner component to a standard file format.
From the tool's definition Tool name 'export_palette_component' and description 'Save a COMP as a .tox into TouchDesigner' indicate the tool creates/persists a file artifact (.tox format) from a component.
Attacks that exploit this kind of access
The rule that runs export_palette_component 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 export_palette_component, this is the rule to start with:
export_palette_component 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 export_palette_component call is checked against it from then on.
Questions about export_palette_component
Save a COMP as a .tox into TouchDesigner. 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 export_palette_component: 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.
export_palette_component 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 export_palette_component 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 export_palette_component. 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.
export_palette_component 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