AI agents call get_midi_info to retrieve information from MIDI File MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about a MIDI file—a pure read operation with no side effects, data modification, or external execution. Even if an AI agent calls it with arbitrary inputs, it can only return file information, posing minimal risk. The low severity reflects that MIDI file metadata exposure is unlikely to cause significant harm.
From the tool's definition Tool name 'get_midi_info' and description 'Get midi file info' indicate a retrieval operation that queries MIDI file metadata without modifying or executing external code. The server description confirms this is among 'read, analyze' operations.
Documented attack patterns abuse exactly the kind of access get_midi_info 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 get_midi_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_midi_info": {}
}
}get_midi_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get midi file info. It is categorised as a Read tool in the MIDI File MCP MCP Server, which means it retrieves data without modifying state.
Register the MIDI File MCP server in PolicyLayer and add a rule for get_midi_info: 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.
get_midi_info 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 get_midi_info 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 get_midi_info. 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.
get_midi_info 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.