Apply a low-pass filter to remove high frequencies above the cutoff.
AI agents invoke effect_low_pass_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 actively processes and modifies audio data by applying a filter effect. It is an audio transformation operation that alters the existing audio content (removing high frequencies), making it an Execute-level action rather than a simple Write, as it runs an audio processing operation with potentially irreversible in-session effects on the audio signal.
From the tool's definition Apply a low-pass filter to remove high frequencies above the cutoff
Documented attack patterns abuse exactly the kind of access effect_low_pass_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_low_pass_filter:
{
"version": "1",
"default": "deny",
"tools": {
"effect_low_pass_filter": {
"limits": [
{
"counter": "effect_low_pass_filter_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}effect_low_pass_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.
Apply a low-pass filter to remove high frequencies above the cutoff. 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_low_pass_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_low_pass_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_low_pass_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_low_pass_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_low_pass_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.