Remove a specific frequency (e.g. 50/60Hz hum) with a notch filter.
AI agents invoke effect_notch_filter to trigger actions in AudacityMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool applies an audio processing effect (notch filter) to audio data in Audacity, transforming the audio by removing specific frequencies. It executes an operation that modifies audio in a way that depends on arguments (frequency to notch), classifying it as Execute. While it modifies data, it's a reversible audio effect (Audacity supports undo), so it doesn't reach Destructive severity.
From the tool's definition Remove a specific frequency (e.g. 50/60Hz hum) with a notch filter
Documented attack patterns abuse exactly the kind of access effect_notch_filter 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 effect_notch_filter:
{
"version": "1",
"default": "deny",
"tools": {
"effect_notch_filter": {
"limits": [
{
"counter": "effect_notch_filter_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}effect_notch_filter stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Remove a specific frequency (e.g. 50/60Hz hum) with a notch filter. It is categorised as a Execute tool in the AudacityMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Audacity MCP server in PolicyLayer and add a rule for effect_notch_filter: 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.
effect_notch_filter is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the effect_notch_filter 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 effect_notch_filter. 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.
effect_notch_filter 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.