AI agents use create_scene to create or update resources in Ableton — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ableton environment.
This tool creates a new scene in Ableton Live, which is a data structure that can be modified or deleted later. Creating a scene is a write operation that modifies the session state but is fully reversible (the scene can be deleted). It does not execute arbitrary code, delete irreversibly, move financial assets, or trigger external operations with unpredictable effects.
From the tool's definition Tool name 'create_scene' and description 'Create a new scene' indicate a create operation that adds a new reversible element to an Ableton Live session.
Documented attack patterns abuse exactly the kind of access create_scene gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ableton, and nothing reaches the server without passing your rules. This is the rule we recommend for create_scene:
{
"version": "1",
"default": "deny",
"tools": {
"create_scene": {
"limits": [
{
"counter": "create_scene_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_scene 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.
Free to start. No card required.
Create a new scene. It is categorised as a Write tool in the Ableton 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. 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 (jpoindexter/ableton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ableton, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
128 Ableton tools catalogued and risk-classified — across an index of 43,000+ MCP servers.