get_track_routing

Get input/output routing info for a track. Use negative track_index for return tracks (-1=A, -2=B).

SERVERLivepilot SOURCElivepilot

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_track_routing does on Livepilot

AI agents call get_track_routing to retrieve information from Livepilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_track_routing is rated Low

This tool queries and retrieves routing configuration metadata from an Ableton Live track. It performs a read-only lookup operation with no side effects, no code execution, and no data modification. The negative track_index parameter is simply a parameter for specifying return tracks, not an indicator of destructive behavior.

From the tool's definition Tool name 'get_track_routing' and description 'Get input/output routing info for a track' explicitly indicates a retrieval operation with no modification or execution of external processes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_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 get_track_routing, this is the rule to start with:

get_track_routing Allowed

get_track_routing is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_track_routing": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_track_routing

What does the get_track_routing tool do? +

Get input/output routing info for a track. Use negative track_index for return tracks (-1=A, -2=B). It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_track_routing? +

Register the Livepilot MCP server in PolicyLayer and add a rule for get_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 get_track_routing? +

get_track_routing is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_track_routing? +

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

Set action: deny in the PolicyLayer policy for get_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 get_track_routing? +

get_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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →