Delete the selected audio without closing the gap (leaves silence where audio was).
AI agents call edit_split_delete 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.
The tool permanently deletes selected audio content. Although it leaves silence in place (rather than closing the gap), the original audio data is removed and cannot be recovered through this operation alone, making it a destructive action. Misuse by an AI agent could irreversibly destroy audio segments in an active project.
From the tool's definition Delete the selected audio without closing the gap (leaves silence where audio was)
Documented attack patterns abuse exactly the kind of access edit_split_delete 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_delete:
{
"version": "1",
"default": "deny",
"hide": [
"edit_split_delete"
]
}edit_split_delete 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.
Delete the selected audio without closing the gap (leaves silence where audio was). 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 edit_split_delete: 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_delete 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 edit_split_delete 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_delete. 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_delete 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.