Set the send level from a track to a return track.
AI agents use set_send_level 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 modifies audio routing configuration by adjusting send levels, which changes how audio signals flow between tracks and returns. This is a reversible write operation (the send level can be adjusted back to its previous value), not a destructive action. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or involve financial transactions (Financial).
From the tool's definition The tool description states 'Set the send level from a track to a return track,' which modifies track routing parameters. This is a configuration change to Ableton Live session state.
Documented attack patterns abuse exactly the kind of access set_send_level 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 set_send_level:
{
"version": "1",
"default": "deny",
"tools": {
"set_send_level": {
"limits": [
{
"counter": "set_send_level_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_send_level 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.
Set the send level from a track to a return track. 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 set_send_level: 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.
set_send_level 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 set_send_level 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 set_send_level. 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.
set_send_level 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.