export_audio · FluidSynth MCP Server MCP: Risk & Policy

WHAT IT DOES

What export_audio does on FluidSynth MCP Server

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

The tool creates and exports audio output, which is a reversible write operation (files can be deleted or overwritten). While the description is empty, the name and context from sibling tools and server description strongly suggest it generates audio files. This is Write rather than Destructive because export operations are typically non-destructive additions to the file system.

From the tool's definition Tool name 'export_audio' combined with sibling tool 'export_midi' and the server's stated capability to 'export audio' indicates this tool writes/generates and outputs audio files to storage.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_audio Rate-limited

export_audio 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_audio": {
      "limits": [
        {
          "counter": "export_audio_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_audio

What does the export_audio tool do? +

export_audio. 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_audio? +

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

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

Can I rate-limit export_audio? +

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

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

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