add_clip_marker

A write tool on the Aos MCP server.

SERVERAos SOURCE@hybridlabor-api/aos

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/add-clip-marker.md

WHAT IT DOES

What add_clip_marker does on Aos

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

RISK

Why add_clip_marker is rated Medium

Adding a marker is a reversible modification operation that creates metadata within a DaVinci Resolve project. While markers can organize and annotate clips, they do not execute external code, delete data, or cause financial impact. This aligns with Write category—creating or modifying data that can be undone.

From the tool's definition Tool name 'add_clip_marker' indicates creation of marker metadata on a video clip. Sibling tools like 'add_clip_flag', 'add_keyframe', and 'add_render_job' are all Write operations that create or modify timeline/project state reversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add_clip_marker 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 add_clip_marker, this is the rule to start with:

add_clip_marker Rate-limited

add_clip_marker 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": {
    "add_clip_marker": {
      "limits": [
        {
          "counter": "add_clip_marker_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every add_clip_marker call is checked against it from then on.

FAQ

Questions about add_clip_marker

What does the add_clip_marker tool do? +

add_clip_marker is a write tool on the Aos MCP server. 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.

How do I enforce a policy on add_clip_marker? +

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

What risk level is add_clip_marker? +

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

Can I rate-limit add_clip_marker? +

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

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

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

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →