duplicate_notes

Duplicate specific notes by ID (JSON array of ints), with optional time offset (in beats).

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-notes.md

WHAT IT DOES

What duplicate_notes does on Livepilot

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

Duplicating notes creates new data in the arrangement/clip without destroying existing notes. This is a reversible write operation (notes can be deleted), not destructive. Misuse could clutter a session but has limited blast radius.

From the tool's definition 'Duplicate specific notes by ID' — creates new note copies with optional time offset

Attacks that exploit this kind of access

RECOMMENDED RULE

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

duplicate_notes Rate-limited

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

FAQ

Questions about duplicate_notes

What does the duplicate_notes tool do? +

Duplicate specific notes by ID (JSON array of ints), with optional time offset (in beats). 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_notes? +

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

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

Can I rate-limit duplicate_notes? +

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

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

duplicate_notes 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

notes_create on Apple Apps MCP → The MCP Attack Database →

Guides

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