Add specified file/folder paths from Media Storage into current Media Pool folder. Args: file_paths: Simple form — list of absolute file/folder paths. item_infos: Positioned form — list of dicts with keys media (required), startFrame, endFrame. Mirrors MediaStorage.AddItemListToMediaPool([{itemIn...
AI agents use add_items_to_media_pool_from_storage to create or update resources in DaVinci Resolve MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DaVinci Resolve MCP environment.
This tool creates/modifies the media pool by adding items from storage—a reversible write operation. It does not execute arbitrary code, delete data, or move financial resources. The severity is medium because misuse could add unwanted large files, corrupt project structure, or cause resource exhaustion, but these effects are reversible by removing the items.
From the tool's definition Tool description states it will 'Add specified file/folder paths from Media Storage into current Media Pool folder,' indicating creation/modification of the Media Pool contents.
Documented attack patterns abuse exactly the kind of access add_items_to_media_pool_from_storage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DaVinci Resolve MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_items_to_media_pool_from_storage:
{
"version": "1",
"default": "deny",
"tools": {
"add_items_to_media_pool_from_storage": {
"limits": [
{
"counter": "add_items_to_media_pool_from_storage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_items_to_media_pool_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.
Free to start. No card required.
Add specified file/folder paths from Media Storage into current Media Pool folder. Args: file_paths: Simple form — list of absolute file/folder paths. item_infos: Positioned form — list of dicts with keys media (required), startFrame, endFrame. Mirrors MediaStorage.AddItemListToMediaPool([{itemInfo}, ...]) per docs line 210. It is categorised as a Write tool in the DaVinci Resolve MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for add_items_to_media_pool_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 DaVinci Resolve MCP. Nothing to install.
add_items_to_media_pool_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 add_items_to_media_pool_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 add_items_to_media_pool_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.
add_items_to_media_pool_from_storage is provided by the DaVinci Resolve MCP server (samuelgursky/davinci-resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 369 DaVinci Resolve MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
369 DaVinci Resolve MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.