import_media_from_storage
Import media files from Resolve's Media Storage into the current media pool folder.
This record as markdown: /tools/hybridlabor-api-aos/import-media-from-storage.md
What import_media_from_storage does on Aos
AI agents use import_media_from_storage 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 import_media_from_storage is rated Medium
Creates new media references reversibly; modifies project state without deleting source data.
From the tool's definition Import media files from Resolve's Media Storage into current media pool folder.
Attacks that exploit this kind of access
The rule that runs import_media_from_storage 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 import_media_from_storage, this is the rule to start with:
import_media_from_storage 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 import_media_from_storage call is checked against it from then on.
Questions about import_media_from_storage
Import media files from Resolve's Media Storage into the current media pool folder. 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 import_media_from_storage: 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.
import_media_from_storage 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 import_media_from_storage 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 import_media_from_storage. 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.
import_media_from_storage 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