List all available soundfonts from soundfontSources.json.
AI agents call list_soundfonts to retrieve information from FluidSynth MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about available soundfonts without creating, modifying, or deleting any data. It is a read-only operation that queries configuration data, fitting the Read category. The blast radius is minimal—misuse could only expose information about available soundfonts, not cause system damage or compromise.
From the tool's definition Tool name 'list_soundfonts' and description 'List all available soundfonts' indicate a query/retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
List all available soundfonts from soundfontSources.json. It is categorised as a Read tool in the FluidSynth MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FluidSynth MCP Server MCP server in PolicyLayer and add a rule for list_soundfonts: 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.
list_soundfonts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_soundfonts 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 list_soundfonts. 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.
list_soundfonts 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →