新しいシーンを作成
AI agents use create_scene to create or update resources in Ableton MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ableton MCP environment.
Creating a scene in Ableton Live adds a new structural element to the project but does not execute arbitrary code or delete data. It is a data-creation operation with side effects limited to the project state. The operation is reversible (scenes can be deleted), placing it in the Write category rather than Execute.
From the tool's definition Tool creates a new scene (新しいシーンを作成 = 'create new scene'). This modifies the Ableton Live project state by adding a new scene object, which is a reversible operation.
Attacks that exploit this kind of access
新しいシーンを作成. It is categorised as a Write tool in the Ableton MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ableton MCP server in PolicyLayer and add a rule for create_scene: 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 Ableton MCP. Nothing to install.
create_scene is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_scene 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.
Set action: deny in the PolicyLayer policy for create_scene. 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.
create_scene is provided by the Ableton MCP server (keigotak/abletonmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →