Low Risk

track_get_info

Get information about all tracks in the project (names, types, rates, etc.).

How to control track_get_info ↓

AI agents call track_get_info to retrieve information from AudacityMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves and queries track information only—names, types, sample rates—with no side effects, modification capabilities, or command execution. It is a pure read operation on project metadata, presenting minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'track_get_info' and description 'Get information about all tracks in the project (names, types, rates, etc.)' indicates retrieval of metadata without modification or execution of operations.

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "track_get_info": {}
  }
}

track_get_info is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the track_get_info tool do? +

Get information about all tracks in the project (names, types, rates, etc.). It is categorised as a Read tool in the AudacityMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on track_get_info? +

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

track_get_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit track_get_info? +

Yes. Add a rate_limit block to the track_get_info 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 track_get_info completely? +

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

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