This record as markdown: /tools/cutpilot/relink-asset.md
What relink_asset does on Cutpilot
AI agents use relink_asset 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 relink_asset is rated Medium
Relinking an asset in a video editing context means updating a reference to point to a different source file or resource. This is a modification operation that changes project state but is reversible (can be undone or relinked again). While it affects project composition, it does not irreversibly destroy data, execute arbitrary commands, or move money.
From the tool's definition 'Safely replace one asset' — the tool modifies an asset by substituting it with another, which is a reversible data modification operation typical of Write category actions.
Attacks that exploit this kind of access
The rule that runs relink_asset 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 relink_asset, this is the rule to start with:
relink_asset 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 relink_asset call is checked against it from then on.
Questions about relink_asset
Safely replace one asset. 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 relink_asset: 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.
relink_asset 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 relink_asset 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 relink_asset. 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.
relink_asset 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