transport_toggle_record · Flai MCP: Risk & Policy

WHAT IT DOES

What transport_toggle_record does on Flai

AI agents invoke transport_toggle_record 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_toggle_record needs a policy

This tool triggers an external operation in FL Studio (starting or stopping recording), which is a stateful action in the DAW that can affect audio/MIDI capture. It does not simply read data, nor does it irreversibly delete or overwrite existing content in a typical scenario.

From the tool's definition Toggle recording on/off in FL Studio

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transport_toggle_record Rate-limited

transport_toggle_record 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_toggle_record": {
      "limits": [
        {
          "counter": "transport_toggle_record_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_toggle_record

What does the transport_toggle_record tool do? +

Toggle recording on/off 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_toggle_record? +

Register the Flai MCP server in PolicyLayer and add a rule for transport_toggle_record: 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_toggle_record? +

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

Can I rate-limit transport_toggle_record? +

Yes. Add a rate_limit block to the transport_toggle_record 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_toggle_record completely? +

Set action: deny in the PolicyLayer policy for transport_toggle_record. 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_toggle_record? +

transport_toggle_record 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.