AI agents use set_channel_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.
This tool modifies audio mixer parameters (stereo panning) which affects how the music production project sounds, but the change is fully reversible (pan can be adjusted back). It does not execute code, delete data, or involve financial transactions. Write is the appropriate category, with medium severity reflecting that incorrect pan settings could degrade the audio mix quality but can be easily undone.
From the tool's definition Tool name 'set_channel_pan' and description 'Set the stereo pan of a channel' indicate a modification operation that changes mixer channel properties. This creates a reversible change to FL Studio mixer state.
Attacks that exploit this kind of access
Set the stereo pan of a channel. 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_channel_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_channel_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_channel_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_channel_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_channel_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 →