Import an audio file into the current project. Creates a new track.
AI agents use project_import_audio 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.
Importing audio and creating a new track modifies the project state but does not irreversibly delete data or execute arbitrary code. The action is reversible (the track can be removed). While it does interact with the file system to read the audio file, the primary effect is creating/writing project data, making Write the appropriate category.
From the tool's definition Tool description states 'Import an audio file into the current project. Creates a new track.' — this creates new data structures (a track) within the project, which is a reversible modification.
Documented attack patterns abuse exactly the kind of access project_import_audio 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_import_audio:
{
"version": "1",
"default": "deny",
"tools": {
"project_import_audio": {
"limits": [
{
"counter": "project_import_audio_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}project_import_audio 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.
Import an audio file into the current project. Creates a new track. 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_import_audio: 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_import_audio 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_import_audio 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_import_audio. 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_import_audio 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.