add_notes · FluidSynth MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_notes does on FluidSynth MCP Server

AI agents use add_notes to create or update resources in FluidSynth MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FluidSynth MCP Server environment.

WHY IT NEEDS A POLICY

Why add_notes needs a policy

The tool creates or appends note data to a MIDI project, which is a reversible Write operation. While the description is empty (lowering confidence from higher), the name and server context clearly indicate data modification rather than retrieval, execution, or destruction. Severity is medium because misuse affects only the current music project state, which can be discarded or modified without external impact.

From the tool's definition Tool name 'add_notes' and sibling context (create_project, create_track, export_audio) indicate this tool modifies musical composition data by adding notes to tracks.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_notes Rate-limited

add_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_notes": {
      "limits": [
        {
          "counter": "add_notes_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches FluidSynth MCP Server, so you can run agents against it safely.

FAQ

Questions about add_notes

What does the add_notes tool do? +

add_notes. It is categorised as a Write tool in the FluidSynth MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_notes? +

Register the FluidSynth MCP Server MCP server in PolicyLayer and add a rule for add_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 FluidSynth MCP Server. Nothing to install.

What risk level is add_notes? +

add_notes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_notes? +

Yes. Add a rate_limit block to the add_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.

How do I block add_notes completely? +

Set action: deny in the PolicyLayer policy for add_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.

What MCP server provides add_notes? +

add_notes is provided by the FluidSynth MCP Server MCP server (kimjune01/synth-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.