Medium Risk

select_tracks

Select one or more tracks by index.

How to control select_tracks ↓

AI agents use select_tracks 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.

Medium Risk

Selecting tracks modifies the application state (the selection) in Audacity, which is a reversible write operation. It does not delete, execute code, or have financial implications. The blast radius is low since it only changes which tracks are selected.

From the tool's definition Select one or more tracks by index

Documented attack patterns abuse exactly the kind of access select_tracks 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_tracks:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "select_tracks": {
      "limits": [
        {
          "counter": "select_tracks_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

select_tracks 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.

  1. Create a free account and register AudacityMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the select_tracks tool do? +

Select one or more tracks by index. 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.

How do I enforce a policy on select_tracks? +

Register the Audacity MCP server in PolicyLayer and add a rule for select_tracks: 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.

What risk level is select_tracks? +

select_tracks is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit select_tracks? +

Yes. Add a rate_limit block to the select_tracks 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.

How do I block select_tracks completely? +

Set action: deny in the PolicyLayer policy for select_tracks. 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.

What MCP server provides select_tracks? +

select_tracks 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.

Enforce policy on every AudacityMCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.