オートメーションをクリア（特定パラメータまたは全て）
AI agents call clear_automation to permanently remove resources in Ableton MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing automation removes previously recorded automation data from a track or project. This is a destructive, likely irreversible action that can delete significant creative work. The description explicitly says it can clear all automation ('全て'), making the blast radius high if misused.
From the tool's definition 'クリア' means 'clear' in Japanese — the tool clears automation data (specific parameters or all). Clearing automation is an irreversible removal of recorded parameter data.
Attacks that exploit this kind of access
オートメーションをクリア（特定パラメータまたは全て）. It is categorised as a Destructive tool in the Ableton MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ableton MCP server in PolicyLayer and add a rule for clear_automation: 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.
clear_automation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_automation 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 clear_automation. 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.
clear_automation 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 →