set_track_name · Flai MCP: Risk & Policy

WHAT IT DOES

What set_track_name does on Flai

AI agents use set_track_name to create or update resources in Flai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flai environment.

WHY IT NEEDS A POLICY

Why set_track_name needs a policy

Renaming a mixer track is a reversible modification operation that changes metadata without destructive consequences. An AI agent misusing this tool would only affect track naming, which is easily undone and has minimal blast radius in a music production context. This clearly falls under Write rather than other categories.

From the tool's definition Tool name 'set_track_name' and description 'Rename a mixer track' indicate modifying metadata of an existing mixer track. The verb 'set' combined with 'rename' confirms a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_track_name Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_track_name": {
      "limits": [
        {
          "counter": "set_track_name_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 set_track_name

What does the set_track_name tool do? +

Rename a mixer track. It is categorised as a Write tool in the Flai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_track_name? +

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

set_track_name is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_track_name? +

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

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

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