set_track_routing

Set input/output routing for a track by display name. Use negative track_index for return tracks (-1=A, -2=B).

SERVERLivepilot SOURCElivepilot

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/set-track-routing.md

WHAT IT DOES

What set_track_routing does on Livepilot

AI agents use set_track_routing to create or update resources in Livepilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.

RISK

Why set_track_routing is rated Medium

This tool modifies audio track routing configuration, making it a Write operation. It creates or modifies audio routing connections within Ableton Live. While it affects the active mix/session state and could disrupt audio during production, the change is not destructive (routing can be undone/reset) and not financial.

From the tool's definition Tool description explicitly states 'Set input/output routing for a track', which modifies track configuration. The ability to change routing affects signal flow and mixing state but is reversible—routing can be re-configured to restore previous state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_track_routing safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_track_routing, this is the rule to start with:

set_track_routing Rate-limited

set_track_routing 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_track_routing": {
      "limits": [
        {
          "counter": "set_track_routing_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every set_track_routing call is checked against it from then on.

FAQ

Questions about set_track_routing

What does the set_track_routing tool do? +

Set input/output routing for a track by display name. Use negative track_index for return tracks (-1=A, -2=B). It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_track_routing? +

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

What risk level is set_track_routing? +

set_track_routing is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_track_routing? +

Yes. Add a rate_limit block to the set_track_routing 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_track_routing completely? +

Set action: deny in the PolicyLayer policy for set_track_routing. 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_track_routing? +

set_track_routing is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →