Cut the selected audio without closing the gap (leaves silence where audio was).
AI agents use edit_split_cut 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 modifies audio content by removing a section and replacing it with silence—a reversible write operation. It does not permanently delete data (which would be Destructive) since the silence can be edited or the original can be restored via undo. The severity is medium because misuse could damage important audio projects, but the effect is confined to the currently selected project and is undoable.
From the tool's definition Tool name 'edit_split_cut' and description 'Cut the selected audio without closing the gap (leaves silence where audio was)' indicates modification of audio data through cutting/splitting operations.
Documented attack patterns abuse exactly the kind of access edit_split_cut 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_cut:
{
"version": "1",
"default": "deny",
"tools": {
"edit_split_cut": {
"limits": [
{
"counter": "edit_split_cut_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_split_cut 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.
Cut the selected audio without closing the gap (leaves silence where audio was). 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_cut: 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_cut 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_cut 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_cut. 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_cut 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.