AI agents use set_track_pan 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.
The tool modifies mixer track state (pan position) in FL Studio, which is a reversible operation. It does not execute arbitrary code, delete data, or involve financial transactions. It falls under Write category as it adjusts configuration parameters. Severity is medium because misuse could alter audio output in unintended ways, but changes are easily reversible and affect only one track parameter at a time.
From the tool's definition Tool name 'set_track_pan' and description 'Set the stereo pan of a mixer track' indicate modification of mixer track parameters. This is a reversible change to track properties in a music production context.
Attacks that exploit this kind of access
Set the stereo pan of 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.
Register the Flai MCP server in PolicyLayer and add a rule for set_track_pan: 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.
set_track_pan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_track_pan 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 set_track_pan. 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.
set_track_pan 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →