Medium Risk

project_new

Create a new empty Audacity project.

How to control project_new ↓

AI agents use project_new 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

This tool creates a new project in Audacity, which is a write operation. It initializes an empty project structure. The severity is low because it creates an empty project with no existing data at risk, and the action is reversible by simply closing/deleting the project.

From the tool's definition Create a new empty Audacity project

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

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

project_new 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 project_new tool do? +

Create a new empty Audacity project. 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 project_new? +

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

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

Can I rate-limit project_new? +

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

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

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