New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

set_scene_name

Rename a scene. Pass empty string to clear the name.

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-scene-name.md

What set_scene_name does on Livepilot

AI agents use set_scene_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.

Why set_scene_name is rated Medium

This tool modifies metadata (scene name) in Ableton Live without irreversible destruction, code execution, or financial impact. Renaming is a standard Write operation. Severity is low because scene naming has no direct impact on audio output, project integrity, or external systems; the change is easily undone by renaming again.

From the tool's definition Tool description explicitly states 'Rename a scene' — a modification operation. The ability to 'pass empty string to clear the name' confirms reversible data mutation.

Questions about set_scene_name

What does the set_scene_name tool do? +

Rename a scene. Pass empty string to clear the name. 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_scene_name? +

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

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

Can I rate-limit set_scene_name? +

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

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

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

More on Livepilot, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livepilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.