copy_device_state

Copy one A/B state to the other (Live 12.3+).

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/copy-device-state.md

WHAT IT DOES

What copy_device_state does on Livepilot

AI agents use copy_device_state 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 copy_device_state is rated Medium

This tool modifies device configuration by copying parameters from one preset state to another, which is a reversible change (undo is available in Ableton Live). It does not execute arbitrary code, delete data permanently, or move financial resources. The blast radius is limited to a single device's state, making it medium severity.

From the tool's definition Tool description states it 'Copy one A/B state to the other', which modifies device state in Ableton Live. The verb 'copy' in this context means to overwrite one of two alternative device states (A or B), making it a write operation that changes existing data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs copy_device_state 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 copy_device_state, this is the rule to start with:

copy_device_state Rate-limited

copy_device_state 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": {
    "copy_device_state": {
      "limits": [
        {
          "counter": "copy_device_state_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 copy_device_state call is checked against it from then on.

FAQ

Questions about copy_device_state

What does the copy_device_state tool do? +

Copy one A/B state to the other (Live 12.3+). 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 copy_device_state? +

Register the Livepilot MCP server in PolicyLayer and add a rule for copy_device_state: 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 copy_device_state? +

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

Can I rate-limit copy_device_state? +

Yes. Add a rate_limit block to the copy_device_state 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 copy_device_state completely? +

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

copy_device_state 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 →