Split the selected audio into a new track at the selection boundaries.
AI agents use edit_split_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 new data structures (a new track) and modifies the project's audio layout. While it doesn't delete data (which would be Destructive) or execute arbitrary code (Execute), it does alter the project state in a way that persists until undone. This is a Write-category operation: it creates/modifies data reversibly.
From the tool's definition Tool performs 'split' operation that creates a new audio track, modifying the project state by adding a new track object and restructuring audio data. The operation is reversible through undo functionality.
Documented attack patterns abuse exactly the kind of access edit_split_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 edit_split_new:
{
"version": "1",
"default": "deny",
"tools": {
"edit_split_new": {
"limits": [
{
"counter": "edit_split_new_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_split_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.
Split the selected audio into a new track at the selection boundaries. 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 edit_split_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.
edit_split_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 edit_split_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 edit_split_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.
edit_split_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.