Medium Risk

set_track_solo

Solo or unsolo tracks in Pro Tools

How to control set_track_solo ↓

What set_track_solo does on Pro Tools MCP Server

AI agents use set_track_solo to create or update resources in Pro Tools MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pro Tools MCP Server environment.

Medium Risk

Why set_track_solo needs a policy

This tool modifies the solo state of tracks in a Pro Tools session. It's a reversible state change (can be soloed and unsoloed), making it a Write operation. Misuse could disrupt audio monitoring or recording sessions but doesn't destroy data.

From the tool's definition Solo or unsolo tracks in Pro Tools

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

How to control set_track_solo

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_track_solo": {
      "limits": [
        {
          "counter": "set_track_solo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Pro Tools MCP Server — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about set_track_solo

What does the set_track_solo tool do? +

Solo or unsolo tracks in Pro Tools. It is categorised as a Write tool in the Pro Tools MCP Server 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_solo? +

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

What risk level is set_track_solo? +

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

Can I rate-limit set_track_solo? +

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

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

set_track_solo is provided by the Pro Tools MCP Server MCP server (skrul/protools-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pro Tools MCP Server tool call.

Start from Pro Tools MCP Server, 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.

36 Pro Tools MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.