resolve_set_third_party_metadata

WHAT IT DOES

What resolve_set_third_party_metadata does on Resolve

AI agents use resolve_set_third_party_metadata to create or update resources in Resolve — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Resolve environment.

WHY IT NEEDS A POLICY

Why resolve_set_third_party_metadata needs a policy

This tool modifies metadata properties on media clips, which is a reversible write operation. It does not execute code, delete data irreversibly, move money, or expose destructive operations. The severity is medium because unintended metadata modifications could affect project organization, clip identification, or downstream workflows, but the effects are localized to metadata and reversible.

From the tool's definition The tool name is 'resolve_set_third_party_metadata' and the description states it will 'Set third-party metadata on a media pool clip.' The verb 'set' indicates modification of clip metadata properties.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_set_third_party_metadata Rate-limited

resolve_set_third_party_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_set_third_party_metadata": {
      "limits": [
        {
          "counter": "resolve_set_third_party_metadata_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Resolve, so you can run agents against it safely.

FAQ

Questions about resolve_set_third_party_metadata

What does the resolve_set_third_party_metadata tool do? +

Set third-party metadata on a media pool clip. It is categorised as a Write tool in the Resolve MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on resolve_set_third_party_metadata? +

Register the Resolve MCP server in PolicyLayer and add a rule for resolve_set_third_party_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 Resolve. Nothing to install.

What risk level is resolve_set_third_party_metadata? +

resolve_set_third_party_metadata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resolve_set_third_party_metadata? +

Yes. Add a rate_limit block to the resolve_set_third_party_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.

How do I block resolve_set_third_party_metadata completely? +

Set action: deny in the PolicyLayer policy for resolve_set_third_party_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.

What MCP server provides resolve_set_third_party_metadata? +

resolve_set_third_party_metadata is provided by the Resolve MCP server (jenkinsm13/resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.