This record as markdown: /tools/hybridlabor-api-aos/export-lut.md
What export_lut does on Aos
AI agents use export_lut 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_lut is rated Medium
The tool exports a LUT, which creates or writes a new file artifact (reversible file creation). This is a Write operation—data is created and stored, but can be deleted or overwritten. Not Destructive (file creation is reversible), not Execute (no code execution), not Financial.
From the tool's definition Tool name 'export_lut' within DaVinci Resolve MCP context; LUT (Look-Up Table) export creates/writes new files to storage, evidenced by sibling tools like 'apply_lut' and 'apply_color_preset' which manipulate color grading data.
Attacks that exploit this kind of access
The rule that runs export_lut 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_lut, this is the rule to start with:
export_lut 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_lut call is checked against it from then on.
Questions about export_lut
export_lut is a write tool on the Aos MCP server. 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_lut: 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_lut 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_lut 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_lut. 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_lut 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