Remove the currently selected track(s). Select tracks first with track_select.
AI agents call track_remove to permanently remove resources in AudacityMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes audio tracks, which cannot be undone by the tool itself (undo would be a separate operation in Audacity). An AI agent misusing this tool could permanently lose substantial audio content, user recordings, or project work. This is a classic destructive operation with high blast radius in an audio editing context.
From the tool's definition Tool name 'track_remove' combined with description 'Remove the currently selected track(s)' indicates irreversible deletion of audio tracks. The term 'remove' in the context of audio editing means permanent deletion from the project.
Documented attack patterns abuse exactly the kind of access track_remove 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_remove:
{
"version": "1",
"default": "deny",
"hide": [
"track_remove"
]
}track_remove disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove the currently selected track(s). Select tracks first with track_select. It is categorised as a Destructive tool in the AudacityMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Audacity MCP server in PolicyLayer and add a rule for track_remove: 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_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the track_remove 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_remove. 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_remove 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.