AI agents use track_mute_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.
This tool modifies track state (mute status) but does not execute arbitrary code, delete data, or affect other systems. The action is fully reversible—unmute restores the previous state. The blast radius is minimal: in a local audio editing context, muting tracks is a standard non-destructive edit.
From the tool's definition Tool name 'track_mute_all' and description 'Mute all tracks in the project' indicate a reversible state change to audio tracks. Muting is not permanent data deletion or destruction; it toggles a property that can be immediately undone by unmuting.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access track_mute_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_mute_all:
{
"version": "1",
"default": "deny",
"tools": {
"track_mute_all": {
"limits": [
{
"counter": "track_mute_all_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}track_mute_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.
Mute 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_mute_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_mute_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_mute_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_mute_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_mute_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.