export_media_pool_metadata
Export metadata of clips in the current Media Pool folder to a CSV file.
This record as markdown: /tools/samuelgursky-davinci-resolve-mcp/export-media-pool-metadata.md
What export_media_pool_metadata does on DaVinci Resolve MCP
AI agents use export_media_pool_metadata 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.
Why export_media_pool_metadata is rated Medium
This tool generates and writes a CSV file containing metadata about clips. While it modifies the file system by creating a new file, it is reversible (the file can be deleted) and has no destructive impact on the original media or project data. It does not delete, execute commands, or move money, making Write the appropriate category.
From the tool's definition Tool creates/exports metadata to a CSV file ('Export metadata of clips in the current Media Pool folder to a CSV file'), which involves writing data to disk.
Attacks that exploit this kind of access
The rule that runs export_media_pool_metadata safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DaVinci Resolve MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For export_media_pool_metadata, this is the rule to start with:
export_media_pool_metadata 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 DaVinci Resolve MCP, apply this rule, and every export_media_pool_metadata call is checked against it from then on.
Questions about export_media_pool_metadata
Export metadata of clips in the current Media Pool folder to a CSV file. 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 export_media_pool_metadata: 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.
export_media_pool_metadata 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_media_pool_metadata 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_media_pool_metadata. 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_media_pool_metadata 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.
More on DaVinci Resolve, and thousands of servers like it.
This server
Across the catalogue