Cut the selected audio to clipboard. Select a region first.
AI agents use edit_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.
While 'cut' might initially suggest destructive behavior, cutting to clipboard is a standard reversible edit operation. The audio remains in clipboard and can be pasted back. This is less severe than permanent deletion (Destructive) but modifies project state (Write). Severity is medium rather than low because unintended cuts could remove significant audio work from a project, though recovery is possible via undo.
From the tool's definition Tool name 'edit_cut' and description 'Cut the selected audio to clipboard' indicates the action removes audio from the project and places it in clipboard memory.
Documented attack patterns abuse exactly the kind of access edit_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_cut:
{
"version": "1",
"default": "deny",
"tools": {
"edit_cut": {
"limits": [
{
"counter": "edit_cut_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_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 to clipboard. Select a region 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 edit_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_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_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_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_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.