High Risk →

set_song_time

Jump playback to a position. Parameters: - bar: Bar number (1-based). Takes precedence over beat. - beat: Beat position (0-based).

How to control set_song_time ↓

AI agents invoke set_song_time to trigger actions in Ableton MCP Extended. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

This tool controls playback position in Ableton Live, which is an external operation that changes the DAW's transport state. It doesn't read, write persistent data, or delete anything, but it does trigger a real-time action in external software. Severity is low because misuse only affects playback position, which is easily corrected.

From the tool's definition 'Jump playback to a position' — triggers an external operation in Ableton Live affecting playback transport state

Documented attack patterns abuse exactly the kind of access set_song_time gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Ableton MCP Extended, and nothing reaches the server without passing your rules. This is the rule we recommend for set_song_time:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_song_time": {
      "limits": [
        {
          "counter": "set_song_time_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

set_song_time stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Ableton MCP Extended — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the set_song_time tool do? +

Jump playback to a position. Parameters: - bar: Bar number (1-based). Takes precedence over beat. - beat: Beat position (0-based). It is categorised as a Execute tool in the Ableton MCP Extended MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_song_time? +

Register the Ableton MCP Extended MCP server in PolicyLayer and add a rule for set_song_time: 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 Extended. Nothing to install.

What risk level is set_song_time? +

set_song_time is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit set_song_time? +

Yes. Add a rate_limit block to the set_song_time 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.

How do I block set_song_time completely? +

Set action: deny in the PolicyLayer policy for set_song_time. 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.

What MCP server provides set_song_time? +

set_song_time is provided by the Ableton MCP Extended MCP server (uisato/ableton-mcp-extended). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ableton MCP Extended tool call.

Deterministic rules across all 46 Ableton MCP Extended tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

46 Ableton MCP Extended tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.