clear_timeline_mark_in_out
Clear mark in/out points on the current timeline.
This record as markdown: /tools/hybridlabor-api-aos/clear-timeline-mark-in-out.md
What clear_timeline_mark_in_out does on Aos
AI agents use clear_timeline_mark_in_out 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 clear_timeline_mark_in_out is rated Medium
Clears timeline markers reversibly; modifies project state but doesn't delete media.
From the tool's definition Clear mark in/out points on the current timeline
Attacks that exploit this kind of access
The rule that runs clear_timeline_mark_in_out 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 clear_timeline_mark_in_out, this is the rule to start with:
clear_timeline_mark_in_out 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 clear_timeline_mark_in_out call is checked against it from then on.
Questions about clear_timeline_mark_in_out
Clear mark in/out points on 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 clear_timeline_mark_in_out: 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.
clear_timeline_mark_in_out 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 clear_timeline_mark_in_out 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 clear_timeline_mark_in_out. 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.
clear_timeline_mark_in_out 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