This record as markdown: /tools/hybridlabor-api-aos/add-track.md
What add_track does on Aos
AI agents use add_track 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_track is rated Medium
This tool creates new data structures (timeline tracks) within a DaVinci Resolve project. It is a Write operation because it modifies project state in a reversible manner—tracks can be deleted or modified later. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool name is 'add_track' and description states it will 'Add a new track to the current timeline.' This creates a new timeline track, which is a reversible modification to the project structure.
Attacks that exploit this kind of access
The rule that runs add_track 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_track, this is the rule to start with:
add_track 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_track call is checked against it from then on.
Questions about add_track
Add a new track to the current timeline. 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_track: 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_track 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_track 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_track. 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_track 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