Add a new track to midi file and return the new track info
AI agents use add_track to create or update resources in MIDI File MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MIDI File MCP environment.
This tool creates new tracks in MIDI files, which is a reversible write operation. It does not execute arbitrary code, delete data, or commit financial transactions. The severity is medium because misuse could corrupt a MIDI file's structure or add unwanted tracks, but the operation is reversible by removing the track or reloading the original file.
From the tool's definition Tool name 'add_track' and description 'Add a new track to midi file' indicate creation of new data within a MIDI file. The broader server description confirms 'modifying tracks' and 'modify MIDI files' as supported operations.
Documented attack patterns abuse exactly the kind of access add_track gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MIDI File MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_track:
{
"version": "1",
"default": "deny",
"tools": {
"add_track": {
"limits": [
{
"counter": "add_track_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_track 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.
Free to start. No card required.
Add a new track to midi file and return the new track info. It is categorised as a Write tool in the MIDI File MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MIDI File MCP server in PolicyLayer and add a rule for add_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 MIDI File MCP. Nothing to install.
add_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 add_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 add_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.
add_track is provided by the MIDI File MCP server (xiaolaa2/midi-file-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MIDI File MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 MIDI File MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.