AI agents call list_midi_ports to retrieve information from FL Studio MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely enumerates available MIDI ports on the system. It has no side effects, creates no data, executes no code, and poses no destructive or financial risk. It is a pure read operation to discover system configuration, consistent with the 'Read' category for retrieval and query operations.
From the tool's definition Tool name is 'list_midi_ports' and description states 'List all available MIDI input ports' — this is a query operation that retrieves information about system MIDI ports without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access list_midi_ports gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FL Studio MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_midi_ports:
{
"version": "1",
"default": "deny",
"tools": {
"list_midi_ports": {}
}
}list_midi_ports 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.
List all available MIDI input ports. It is categorised as a Read tool in the FL Studio MCP MCP Server, which means it retrieves data without modifying state.
Register the FL Studio MCP server in PolicyLayer and add a rule for list_midi_ports: 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 FL Studio MCP. Nothing to install.
list_midi_ports 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_midi_ports 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_midi_ports. 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_midi_ports is provided by the FL Studio MCP server (veenastudio/flstudio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 FL Studio MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 FL Studio MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.