duplicate_scene

Duplicate a scene (copies all clip slots).

SERVERLivepilot SOURCElivepilot

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/duplicate-scene.md

WHAT IT DOES

What duplicate_scene does on Livepilot

AI agents use duplicate_scene to create or update resources in Livepilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.

RISK

Why duplicate_scene is rated Medium

Duplicating a scene creates a new copy of existing data (all clip slots), which is a reversible write operation. It does not delete or overwrite existing data, nor does it execute code or involve financial transactions. The blast radius is medium since misuse could clutter the arrangement but is easily undone.

From the tool's definition Duplicate a scene (copies all clip slots)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs duplicate_scene safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For duplicate_scene, this is the rule to start with:

duplicate_scene Rate-limited

duplicate_scene 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "duplicate_scene": {
      "limits": [
        {
          "counter": "duplicate_scene_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every duplicate_scene call is checked against it from then on.

FAQ

Questions about duplicate_scene

What does the duplicate_scene tool do? +

Duplicate a scene (copies all clip slots). It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on duplicate_scene? +

Register the Livepilot MCP server in PolicyLayer and add a rule for duplicate_scene: 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 Livepilot. Nothing to install.

What risk level is duplicate_scene? +

duplicate_scene is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit duplicate_scene? +

Yes. Add a rate_limit block to the duplicate_scene 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.

How do I block duplicate_scene completely? +

Set action: deny in the PolicyLayer policy for duplicate_scene. 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.

What MCP server provides duplicate_scene? +

duplicate_scene is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →