transport_play · Flai MCP: Risk & Policy

WHAT IT DOES

What transport_play does on Flai

AI agents invoke transport_play to trigger actions in Flai. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why transport_play needs a policy

This tool executes an external operation (starting playback in FL Studio) whose effects depend on the state of the DAW and loaded project. While not destructive or financial, it performs an action rather than retrieving data. It is Execute rather than Write because it does not create or modify persistent data in the project itself — playback is a transient operational state.

From the tool's definition Tool name and description: 'Start playback in FL Studio' — initiates playback action which is an external operation that triggers FL Studio's transport controls.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transport_play Rate-limited

transport_play stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transport_play": {
      "limits": [
        {
          "counter": "transport_play_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Flai, so you can run agents against it safely.

FAQ

Questions about transport_play

What does the transport_play tool do? +

Start playback in FL Studio. It is categorised as a Execute tool in the Flai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on transport_play? +

Register the Flai MCP server in PolicyLayer and add a rule for transport_play: 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 Flai. Nothing to install.

What risk level is transport_play? +

transport_play is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit transport_play? +

Yes. Add a rate_limit block to the transport_play 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.

How do I block transport_play completely? +

Set action: deny in the PolicyLayer policy for transport_play. 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.

What MCP server provides transport_play? +

transport_play is provided by the Flai MCP server (kaupau/flai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.