AI agents use track_unmute_all to create or update resources in AudacityMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AudacityMCP environment.
Unmuting tracks modifies the project state by changing audio track properties, but this is a reversible operation—users can mute tracks again. It does not permanently delete data, execute arbitrary code, trigger financial transactions, or create irreversible changes. This is classified as Write because it modifies project configuration in a non-destructive manner.
From the tool's definition Tool name 'track_unmute_all' and description 'Unmute all tracks in the project' indicate modification of track mute state, which is a reversible state change to audio project configuration.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access track_unmute_all gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AudacityMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for track_unmute_all:
{
"version": "1",
"default": "deny",
"tools": {
"track_unmute_all": {
"limits": [
{
"counter": "track_unmute_all_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}track_unmute_all 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.
Unmute all tracks in the project. It is categorised as a Write tool in the AudacityMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Audacity MCP server in PolicyLayer and add a rule for track_unmute_all: 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 AudacityMCP. Nothing to install.
track_unmute_all 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 track_unmute_all 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 track_unmute_all. 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.
track_unmute_all is provided by the Audacity MCP server (xdarkzx/audacity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 131 AudacityMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
131 AudacityMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.