AI agents use select_tracks 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.
Selecting tracks changes the UI/application state in Pro Tools (which tracks are active/selected), but does not delete, execute code, or move money. It is reversible (tracks can be deselected), making it a Write-category action with low blast radius.
From the tool's definition "Select tracks by name in Pro Tools" — modifies the selection state of tracks in the application
Documented attack patterns abuse exactly the kind of access select_tracks gives an agent:
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 select_tracks:
{
"version": "1",
"default": "deny",
"tools": {
"select_tracks": {
"limits": [
{
"counter": "select_tracks_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}select_tracks 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.
Select tracks by name 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.
Register the Pro Tools MCP Server MCP server in PolicyLayer and add a rule for select_tracks: 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.
select_tracks 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 select_tracks 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 select_tracks. 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.
select_tracks 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.
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.