create_track
AI agents use create_track 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.
This tool creates a new music track, which is a reversible write operation that modifies the state of a MIDI composition project by adding data. The severity is medium because while tracks can be created, the sibling tools suggest broader project manipulation capabilities, but individual track creation alone does not have high blast radius.
From the tool's definition Tool name 'create_track' combined with sibling tools that include 'add_notes', 'add_soundfont', 'export_audio', and 'export_midi' indicate this creates new data structures (music tracks) within a MIDI composition system.
Attacks that exploit this kind of access
create_track. 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.
Register the FluidSynth MCP Server MCP server in PolicyLayer and add a rule for create_track: 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.
create_track 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 create_track 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 create_track. 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.
create_track 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 →