Medium Risk

perform_clip_audio_classification

Classify a clip's audio into categories and subcategories (Resolve 21+). Args: clip_id: Unique ID of the clip.

How to control perform_clip_audio_classification ↓

AI agents use perform_clip_audio_classification 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.

Medium Risk

An AI agent can call perform_clip_audio_classification faster than any human can review — one bad instruction and it creates or modifies resources in DaVinci Resolve MCP by the hundred, each call as confident as the last.

Documented attack patterns abuse exactly the kind of access perform_clip_audio_classification 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 perform_clip_audio_classification:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "perform_clip_audio_classification": {
      "limits": [
        {
          "counter": "perform_clip_audio_classification_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register DaVinci Resolve MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the perform_clip_audio_classification tool do? +

Classify a clip's audio into categories and subcategories (Resolve 21+). Args: clip_id: Unique ID of the clip. 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.

How do I enforce a policy on perform_clip_audio_classification? +

Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for perform_clip_audio_classification: 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.

What risk level is perform_clip_audio_classification? +

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

Can I rate-limit perform_clip_audio_classification? +

Yes. Add a rate_limit block to the perform_clip_audio_classification 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 perform_clip_audio_classification completely? +

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

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

Enforce policy on every DaVinci Resolve MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.