Split the selected audio at detected silences, creating separate clips.
AI agents use edit_disjoin 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 the audio project by splitting audio into separate clips at silence points. It creates new clip boundaries (a write/modify operation) but does not delete data — the audio content remains intact. It is reversible via undo in Audacity, making it Write rather than Destructive.
From the tool's definition Split the selected audio at detected silences, creating separate clips.
Documented attack patterns abuse exactly the kind of access edit_disjoin 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_disjoin:
{
"version": "1",
"default": "deny",
"tools": {
"edit_disjoin": {
"limits": [
{
"counter": "edit_disjoin_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_disjoin 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 at detected silences, creating separate clips. 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_disjoin: 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_disjoin 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_disjoin 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_disjoin. 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_disjoin 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.