Mix and render selected tracks into a single track. Select tracks first.
AI agents use track_mix_and_render 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 and modifies audio data by combining tracks into a new rendered output. While the operation is technically reversible via undo, the primary action is to write/create new audio content. It does not delete source tracks (Write rather than Destructive), does not execute arbitrary code (Execute), and does not involve financial transactions.
From the tool's definition Tool performs 'Mix and render selected tracks into a single track' - this creates a new composite audio track from existing tracks, modifying the project state irreversibly in terms of track structure (combining multiple tracks into one).
Documented attack patterns abuse exactly the kind of access track_mix_and_render 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:
{
"version": "1",
"default": "deny",
"tools": {
"track_mix_and_render": {
"limits": [
{
"counter": "track_mix_and_render_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}track_mix_and_render 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 single track. 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: 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 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 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. 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 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.