copy_device_state · Livepilot MCP: Risk & Policy

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.

WHY IT NEEDS A POLICY

Why copy_device_state needs a policy

An AI agent can call copy_device_state faster than any human can review — one bad instruction and it creates or modifies resources in Livepilot by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Livepilot, so you can run agents against it safely.

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.