set_clip_name

Rename a clip in the Session view. The new name appears on the clip slot and in Device Chain displays.

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/set-clip-name.md

WHAT IT DOES

What set_clip_name does on Livepilot

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

Renaming a clip is a write operation that modifies clip properties reversibly without destructive side effects, executing code, financial impact, or data deletion. The scope is limited to a single clip's name attribute, making it low severity even if misused (worst case: user sees confusing clip names).

From the tool's definition Tool description states 'Rename a clip' — a direct modification operation. The name change is reversible and affects only metadata display properties of a clip object in Ableton Live.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_clip_name Rate-limited

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

FAQ

Questions about set_clip_name

What does the set_clip_name tool do? +

Rename a clip in the Session view. The new name appears on the clip slot and in Device Chain displays. 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 set_clip_name? +

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

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

Can I rate-limit set_clip_name? +

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

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

set_clip_name 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

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

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