AI agents use label_add 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 new label metadata in an audio project, which is a write operation. It does not execute arbitrary code, delete data, move money, or have destructive effects. Labels can be easily removed or modified, making this a reversible modification. The blast radius is minimal since labels are non-destructive metadata additions to a project.
From the tool's definition Tool name 'label_add' and description 'Add a label at the current cursor position or selection' indicate creation of metadata/labels within an Audacity project. Labels are reversibly created annotations.
Documented attack patterns abuse exactly the kind of access label_add 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 label_add:
{
"version": "1",
"default": "deny",
"tools": {
"label_add": {
"limits": [
{
"counter": "label_add_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}label_add 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.
Add a label at the current cursor position or selection. 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 label_add: 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.
label_add 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 label_add 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 label_add. 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.
label_add 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.