Mix and render selected tracks into a new track, keeping the originals. Select tracks first.
AI agents use track_mix_and_render_to_new 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 creates a new track by mixing and rendering selected tracks. It is a Write operation because it creates new data (a new rendered track) while preserving the originals. It is reversible in the sense that the originals are kept and the new track could be deleted. Severity is medium because misuse could add unwanted tracks to an audio project, but the originals remain intact.
From the tool's definition Mix and render selected tracks into a new track, keeping the originals
Documented attack patterns abuse exactly the kind of access track_mix_and_render_to_new 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_mix_and_render_to_new:
{
"version": "1",
"default": "deny",
"tools": {
"track_mix_and_render_to_new": {
"limits": [
{
"counter": "track_mix_and_render_to_new_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}track_mix_and_render_to_new 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.
Mix and render selected tracks into a new track, keeping the originals. Select tracks first. 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_mix_and_render_to_new: 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_mix_and_render_to_new 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_mix_and_render_to_new 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_mix_and_render_to_new. 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_mix_and_render_to_new 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.