AI agents use edit_notes 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 tool creates or modifies data reversibly (editing notes in a vocal track). While it affects the project, the changes are not permanent deletions and can be undone, making it a Write operation rather than Destructive. The severity is medium because misuse could corrupt or alter a user's musical project, but the impact is limited to the specific track/notes being edited and is recoverable.
From the tool's definition Tool name is 'edit_notes' and description states 'Edit one or more notes' — modifies existing musical note data within a Synthesizer V project
Documented attack patterns abuse exactly the kind of access edit_notes 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 edit_notes:
{
"version": "1",
"default": "deny",
"tools": {
"edit_notes": {
"limits": [
{
"counter": "edit_notes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_notes 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.
Edit one or more notes. 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 edit_notes: 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.
edit_notes 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 edit_notes 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 edit_notes. 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.
edit_notes 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.