Adjust bass and treble frequencies with a simple tonal shaping tool.
AI agents use effect_bass_and_treble 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 adjusting frequency characteristics (bass and treble), which constitutes a reversible write operation on the audio file. It does not execute arbitrary code, delete data, move money, or perform destructive operations.
From the tool's definition Tool name 'effect_bass_and_treble' and description 'Adjust bass and treble frequencies' indicates modification of audio data. The verb 'Adjust' combined with audio frequency parameters confirms data is being modified.
Documented attack patterns abuse exactly the kind of access effect_bass_and_treble 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_bass_and_treble:
{
"version": "1",
"default": "deny",
"tools": {
"effect_bass_and_treble": {
"limits": [
{
"counter": "effect_bass_and_treble_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}effect_bass_and_treble 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.
Adjust bass and treble frequencies with a simple tonal shaping tool. 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 effect_bass_and_treble: 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_bass_and_treble 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 effect_bass_and_treble 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_bass_and_treble. 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_bass_and_treble 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.