This record as markdown: /tools/hybridlabor-api-aos/add-marker.md
What add_marker does on Aos
AI agents use add_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.
Why add_marker is rated Medium
Adding a marker creates new data in the project file (marker metadata, timestamps, labels) but is reversible—markers can be deleted. This is a Write operation, not Destructive. Severity is medium because unauthorized marker additions could clutter projects and waste editor time, but cause no permanent data loss.
From the tool's definition Tool name 'add_marker' in a video editing context (DaVinci Resolve) indicates creation of metadata (markers) on timeline elements.
Attacks that exploit this kind of access
The rule that runs add_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_marker, this is the rule to start with:
add_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every add_marker call is checked against it from then on.
Questions about add_marker
add_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.
Register the Aos MCP server in PolicyLayer and add a rule for add_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.
add_marker 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_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.
Set action: deny in the PolicyLayer policy for add_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.
add_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.
More on Aos, and thousands of servers like it.
This server
Across the catalogue