AI agents use set_track_mute 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.
This tool modifies the mute state of tracks, which is a reversible write operation. It does not delete data or execute code, and can be undone by toggling the mute state back. Misuse could disrupt audio sessions but is recoverable.
From the tool's definition Mute or unmute tracks in Pro Tools
Documented attack patterns abuse exactly the kind of access set_track_mute 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 set_track_mute:
{
"version": "1",
"default": "deny",
"tools": {
"set_track_mute": {
"limits": [
{
"counter": "set_track_mute_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_track_mute 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.
Mute or unmute 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.
Register the Pro Tools MCP Server MCP server in PolicyLayer and add a rule for set_track_mute: 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.
set_track_mute 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 set_track_mute 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 set_track_mute. 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.
set_track_mute 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.