mute_track
Mutes or unmutes an entire audio track.
This record as markdown: /tools/adobe-premiere-pro-mcp/mute-track.md
What mute_track does on Adobe Premiere Pro
AI agents use mute_track to create or update resources in Adobe Premiere Pro, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adobe Premiere Pro environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
muted | boolean | Yes | Whether to mute (true) or unmute (false) the track |
sequenceId | string | Yes | The ID of the sequence |
trackIndex | number | Yes | The index of the audio track |
Parameters from the server's own tool schema.
Why mute_track is rated Medium
Muting/unmuting a track is a Write operation because it creates or modifies project state (track properties) reversibly. It is not Destructive (the change can be undone), not Execute (no code or scripts are run), not Read (it modifies rather than just queries), and not Financial.
From the tool's definition The tool description states it 'Mutes or unmutes an entire audio track' — this modifies the state of an audio track in Adobe Premiere Pro, which is a reversible change to project data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs mute_track safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adobe Premiere Pro, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mute_track, this is the rule to start with:
mute_track 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Adobe Premiere Pro, apply this rule, and every mute_track call is checked against it from then on.
Questions about mute_track
Mutes or unmutes an entire audio track. It is categorised as a Write tool in the Adobe Premiere Pro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mute_track accepts 3 parameters: muted, sequenceId, trackIndex. Required: muted, sequenceId, trackIndex. The full parameter table on this page comes from the server's own tool schema.
Register the Adobe Premiere Pro MCP server in PolicyLayer and add a rule for mute_track: 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 Adobe Premiere Pro. Nothing to install.
mute_track 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 mute_track 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 mute_track. 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.
mute_track is provided by the Adobe Premiere Pro MCP server (adobe-premiere-pro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adobe Premiere Pro, and thousands of servers like it.
This server
Across the catalogue