Remove clicks and pops from the selected audio (e.g. vinyl recordings).
AI agents use click_removal 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 data by removing artifacts (clicks and pops), which is a reversible write/edit operation on the selected audio. It does not delete files or execute arbitrary code, but it does alter the audio content. Severity is medium since misuse could corrupt or undesirably alter audio recordings, but effects are typically reversible via undo.
From the tool's definition Remove clicks and pops from the selected audio
Documented attack patterns abuse exactly the kind of access click_removal 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 click_removal:
{
"version": "1",
"default": "deny",
"tools": {
"click_removal": {
"limits": [
{
"counter": "click_removal_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}click_removal 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.
Remove clicks and pops from the selected audio (e.g. vinyl recordings). 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 click_removal: 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.
click_removal 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 click_removal 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 click_removal. 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.
click_removal 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.