AI agents use select_none 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.
Deselecting audio changes the active selection in Audacity but does not create, delete, or execute arbitrary code. It is a reversible state modification (Write category) with minimal blast radius—the worst outcome is that the user must reselect audio. This is low severity because it has no destructive or financial impact and the action is easily undone.
From the tool's definition Tool name 'select_none' and description 'Deselect all audio' indicate modification of the current selection state in Audacity, which is a reversible editor state change.
Documented attack patterns abuse exactly the kind of access select_none 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 select_none:
{
"version": "1",
"default": "deny",
"tools": {
"select_none": {
"limits": [
{
"counter": "select_none_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}select_none 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.
Deselect all audio. 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 select_none: 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.
select_none 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 select_none 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 select_none. 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.
select_none 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.