export_midi · FluidSynth MCP Server MCP: Risk & Policy

WHAT IT DOES

What export_midi does on FluidSynth MCP Server

AI agents use export_midi 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 export_midi needs a policy

This tool creates/generates a new file artifact (MIDI format) from existing project data. While it produces output, it does not execute arbitrary code, delete data, move money, or perform destructive operations. The severity is low because file export operations have minimal blast radius—the worst case is creation of unintended MIDI files, which are easily deleted and pose no system compromise risk.

From the tool's definition The tool name 'export_midi' and description 'Export a project as a MIDI file' indicate creation and output of a data artifact (a MIDI file). The verb 'export' combined with file creation semantics places this in the Write category.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_midi Rate-limited

export_midi 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": {
    "export_midi": {
      "limits": [
        {
          "counter": "export_midi_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 export_midi

What does the export_midi tool do? +

Export a project as a MIDI file. 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 export_midi? +

Register the FluidSynth MCP Server MCP server in PolicyLayer and add a rule for export_midi: 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 export_midi? +

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

Can I rate-limit export_midi? +

Yes. Add a rate_limit block to the export_midi 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 export_midi completely? +

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

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