AI agents use add_track to create or update resources in Mcp Svstudio — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Svstudio environment.
This is a Write action because it creates new structured data (a music track) that is reversible—tracks can be deleted or modified later. It does not execute arbitrary code, delete data, or move money. Severity is medium because misuse could result in unwanted track creation or project clutter, but the effect is contained to the project and easily undone.
From the tool's definition Tool description states 'Add a new track to the project' — creates new data/content within the Synthesizer V project without deletion or irreversible consequences.
Documented attack patterns abuse exactly the kind of access add_track gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Svstudio, and nothing reaches the server without passing your rules. This is the rule we recommend for add_track:
{
"version": "1",
"default": "deny",
"tools": {
"add_track": {
"limits": [
{
"counter": "add_track_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_track 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 new track to the project. It is categorised as a Write tool in the Mcp Svstudio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Svstudio MCP server in PolicyLayer and add a rule for add_track: 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 Mcp Svstudio. Nothing to install.
add_track 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 add_track 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 add_track. 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.
add_track is provided by the Mcp Svstudio MCP server (ocadaruma/mcp-svstudio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Svstudio, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Mcp Svstudio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.