Change speed of the selected audio (changes both tempo and pitch together).
AI agents use effect_change_speed 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 altering its speed (and consequently tempo and pitch). It is a reversible transformation applied to selected audio within Audacity, making it a Write-category action. Misuse could alter audio content unintentionally, giving it medium severity.
From the tool's definition Change speed of the selected audio (changes both tempo and pitch together)
Documented attack patterns abuse exactly the kind of access effect_change_speed 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_change_speed:
{
"version": "1",
"default": "deny",
"tools": {
"effect_change_speed": {
"limits": [
{
"counter": "effect_change_speed_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}effect_change_speed 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.
Change speed of the selected audio (changes both tempo and pitch together). 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_change_speed: 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_change_speed 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_change_speed 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_change_speed. 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_change_speed 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.