Save the current Audacity project. ONLY call this when the user explicitly asks to save.
AI agents use project_save 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.
Saving a project modifies or writes data to the file system. It is reversible (files can be edited again or deleted), so it does not qualify as Destructive. The tool does not execute arbitrary code or trigger external operations (Execute), nor does it involve financial transactions. Write is the appropriate category.
From the tool's definition Tool name is 'project_save' and description states it 'Save[s] the current Audacity project.' This persists modified audio data to disk.
Documented attack patterns abuse exactly the kind of access project_save 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:
{
"version": "1",
"default": "deny",
"tools": {
"project_save": {
"limits": [
{
"counter": "project_save_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}project_save 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 Audacity project. ONLY call this when the user explicitly asks to save. 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: 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 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 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. 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 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.