move_asset_bin
Move an asset bin to the root or another parent while preventing hierarchy cycles.
This record as markdown: /tools/cutpilot/move-asset-bin.md
What move_asset_bin does on Cutpilot
AI agents use move_asset_bin to create or update resources in Cutpilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cutpilot environment.
Why move_asset_bin is rated Medium
This tool creates or modifies the organizational structure of video assets by relocating asset bins within a project hierarchy. The operation is reversible (bins can be moved again) and has no permanent deletion or financial implications. It is less severe than Execute because it performs a specific data modification rather than arbitrary code execution.
From the tool's definition Tool description states "Move an asset bin to the root or another parent" - this modifies the hierarchical structure and location of data assets within a video editing project, which is a reversible write operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs move_asset_bin safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cutpilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_asset_bin, this is the rule to start with:
move_asset_bin 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 Cutpilot, apply this rule, and every move_asset_bin call is checked against it from then on.
Questions about move_asset_bin
Move an asset bin to the root or another parent while preventing hierarchy cycles. It is categorised as a Write tool in the Cutpilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cutpilot MCP server in PolicyLayer and add a rule for move_asset_bin: 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 Cutpilot. Nothing to install.
move_asset_bin 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 move_asset_bin 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 move_asset_bin. 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.
move_asset_bin is provided by the Cutpilot MCP server (Hellotravisss/cutpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cutpilot, and thousands of servers like it.
This server
Across the catalogue