Save the current project to a new .aup3 file. ONLY call when user explicitly asks.
AI agents use project_save_as 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 creates or modifies data (a new project file) in a reversible manner. While it writes to disk, the operation is reversible—the file can be deleted or overwritten later. This places it squarely in the Write category rather than Destructive.
From the tool's definition Tool description states 'Save the current project to a new .aup3 file', which creates/writes a new file to the filesystem. The tool name 'project_save_as' and description confirm it performs a file write operation.
Documented attack patterns abuse exactly the kind of access project_save_as 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_save_as:
{
"version": "1",
"default": "deny",
"tools": {
"project_save_as": {
"limits": [
{
"counter": "project_save_as_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}project_save_as 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.
Save the current project to a new .aup3 file. ONLY call when user explicitly asks. 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 project_save_as: 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.
project_save_as 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 project_save_as 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 project_save_as. 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.
project_save_as 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.