Open the metadata editor dialog to view/edit track metadata (title, artist, etc.).
AI agents use project_edit_metadata 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 metadata reversibly without destructive effects. Changes to metadata (title, artist) can be undone and do not involve deletion or irreversible operations. The scope is limited to metadata fields rather than audio content itself, making it a Write-category operation with low severity since metadata changes have minimal impact on system integrity or data loss risk.
From the tool's definition Tool enables editing of track metadata (title, artist, etc.), which modifies data stored in audio project files. The description explicitly states 'view/edit' indicating data modification capability.
Documented attack patterns abuse exactly the kind of access project_edit_metadata 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_edit_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"project_edit_metadata": {
"limits": [
{
"counter": "project_edit_metadata_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}project_edit_metadata 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.
Open the metadata editor dialog to view/edit track metadata (title, artist, etc.). 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_edit_metadata: 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_edit_metadata 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_edit_metadata 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_edit_metadata. 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_edit_metadata 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.