AI agents use edit_silence 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 replacing sections with silence. While the operation is reversible through Audacity's undo functionality (making it Write rather than Destructive), it directly alters user audio projects and could result in significant data loss if misused by an AI agent—for example, silencing large sections of a podcast, music track, or interview by mistake.
From the tool's definition The tool description states it will 'Replace the selected audio with silence.' This modifies existing audio data by overwriting it with silence, which is a reversible write operation (the original audio can be recovered via undo).
Documented attack patterns abuse exactly the kind of access edit_silence 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_silence:
{
"version": "1",
"default": "deny",
"tools": {
"edit_silence": {
"limits": [
{
"counter": "edit_silence_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_silence 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.
Replace the selected audio with silence. 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_silence: 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_silence 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_silence 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_silence. 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_silence 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.