Lo-Fi Hip Hopプロジェクトを一発で作成(テンプレート)
AI agents use create_lofi_project 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.
This tool creates a new Ableton Live project with predefined Lo-Fi settings. Creation of reversible project structures is a Write operation—it modifies the music production workspace but does not execute arbitrary code, delete data, or trigger external side effects beyond Ableton's own state. The blast radius is limited to the local Ableton session.
From the tool's definition Tool name 'create_lofi_project' and description indicate it creates a new project using a template. The Japanese description translates to 'Create a Lo-Fi Hip Hop project in one shot (template)', confirming project creation/generation.
Attacks that exploit this kind of access
Lo-Fi Hip Hopプロジェクトを一発で作成(テンプレート). 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_lofi_project: 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_lofi_project 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_lofi_project 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_lofi_project. 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_lofi_project 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 →